From: Markus Elfring <Markus.Elfring@web.de>
To: Zhang Qiang <qiang.zhang@windriver.com>,
Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v6] workqueue: Remove unnecessary kfree() call in rcu_free_wq()
Date: Thu, 28 May 2020 10:07:48 +0200 [thread overview]
Message-ID: <4f292007-4da0-3558-4c6b-ca3eaf884193@web.de> (raw)
In-Reply-To: <20200528013736.39356-1-qiang.zhang@windriver.com>
> Thus delete this function call which became unnecessary with the referenced
> software update.
…
> Co-developed-by: Markus Elfring <Markus.Elfring@web.de>
I guess that this tag should usually trigger another consequence like the following.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=b0c3ba31be3e45a130e13b278cf3b90f69bda6f6#n548
Signed-off-by: Markus Elfring <Markus.Elfring@web.de>
Is there a need to tag also the patch review contribution of Lai Jiangshan?
https://lore.kernel.org/lkml/CAJhGHyC4XcNL8yzWZKZ=73wZJej4JwCaAHGV8qjYn-AqcEAEjQ@mail.gmail.com/
https://lore.kernel.org/patchwork/comment/1442889/
https://lkml.org/lkml/2020/5/26/201
I am unsure if such aspects will matter after Tejun Heo responded with the information
“Applied to wq/for-5.8.” to the previous patch version yesterday.
https://lore.kernel.org/lkml/20200527135214.GI83516@mtj.thefacebook.com/
https://lore.kernel.org/patchwork/comment/1443888/
> v1->v2->v3->v4->v5->v6:
> Modify weakly submitted information and tag.
I am curious how our imaginations and preferences will evolve further
also for such wording selections.
Regards,
Markus
prev parent reply other threads:[~2020-05-28 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 1:37 qiang.zhang
2020-05-28 8:07 ` Markus Elfring [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=4f292007-4da0-3558-4c6b-ca3eaf884193@web.de \
--to=markus.elfring@web.de \
--cc=jiangshanlai@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiang.zhang@windriver.com \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®