lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1f3cdf9c-7437-65e7-c226-c53e17a722b7@csgroup.eu>
Date:   Mon, 20 Jun 2022 11:11:33 +0000
From:   Christophe Leroy <christophe.leroy@...roup.eu>
To:     Liang He <windhl@....com>
CC:     "mpe@...erman.id.au" <mpe@...erman.id.au>,
        "benh@...nel.crashing.org" <benh@...nel.crashing.org>,
        "paulus@...ba.org" <paulus@...ba.org>,
        "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
        "rppt@...nel.org" <rppt@...nel.org>,
        "wangkefeng.wang@...wei.com" <wangkefeng.wang@...wei.com>,
        "gpiccoli@...lia.com" <gpiccoli@...lia.com>,
        "aneesh.kumar@...ux.ibm.com" <aneesh.kumar@...ux.ibm.com>,
        "dmitry.osipenko@...labora.com" <dmitry.osipenko@...labora.com>,
        "linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] powerpc: kernel: Change the order of of_node_put()

Hi,

Le 20/06/2022 à 11:23, Liang He a écrit :
> 
> Hi, Christophe.
> 
> Sorry to trobule you again.
> 
> Now I have found other bugs in same directories (i.e., arch/powerpc/sysdev),
> with the ones I have sent but not recieved acked-by or confirmed email.
> 
> So I need to merge the old ones into the new ones as a PATCH-v2 and then resend the
> old ones ?
> or just use a new PATCH to send only new ones?
> 
> I am afraid to make new trouble for maintainers, so can you share your valuable
> experience?
> 

Here is the list of your patches : 
https://patchwork.ozlabs.org/project/linuxppc-dev/list/?submitter=84258

 From my point of view, for all the patches that are still in status 
"new" it is better than you send a v2 with more things into a single 
patch. When the patch is in "under review" state, it is better to not 
update it anymore.

So in the list there are for instance several patches for powernv, so it 
would be good if you can regroup all of them in a single v2 patch.

Christophe

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ