From: "Liang He" <windhl@126.com>
To: "Christophe Leroy" <christophe.leroy@csgroup.eu>
Cc: "mpe@ellerman.id.au" <mpe@ellerman.id.au>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"paulus@samba.org" <paulus@samba.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"rppt@kernel.org" <rppt@kernel.org>,
"wangkefeng.wang@huawei.com" <wangkefeng.wang@huawei.com>,
"gpiccoli@igalia.com" <gpiccoli@igalia.com>,
"aneesh.kumar@linux.ibm.com" <aneesh.kumar@linux.ibm.com>,
"dmitry.osipenko@collabora.com" <dmitry.osipenko@collabora.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re:Re: [PATCH] powerpc: kernel: Change the order of of_node_put()
Date: Mon, 20 Jun 2022 20:27:05 +0800 (CST) [thread overview]
Message-ID: <16a2a6b2.8542.1818114aeea.Coremail.windhl@126.com> (raw)
In-Reply-To: <1f3cdf9c-7437-65e7-c226-c53e17a722b7@csgroup.eu>
At 2022-06-20 19:11:33, "Christophe Leroy" <christophe.leroy@csgroup.eu> wrote:
>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
Thanks, Christophe.
I will follow your rules and try to group the 'new' state ones.
prev parent reply other threads:[~2022-06-20 12:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 11:26 [PATCH] powerpc: kernel: Change the order of of_node_put() Liang He
2022-06-18 7:13 ` Christophe Leroy
2022-06-18 8:03 ` Liang He
2022-06-18 8:48 ` Christophe Leroy
2022-06-18 16:20 ` Liang He
2022-06-20 9:23 ` Liang He
2022-06-20 11:11 ` Christophe Leroy
2022-06-20 12:27 ` Liang He [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16a2a6b2.8542.1818114aeea.Coremail.windhl@126.com \
--to=windhl@126.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=dmitry.osipenko@collabora.com \
--cc=gpiccoli@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=rppt@kernel.org \
--cc=wangkefeng.wang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox