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 v5] workqueue: Remove unnecessary kfree() call in rcu_free_wq()
Date: Wed, 27 May 2020 10:20:46 +0200 [thread overview]
Message-ID: <284c7851-4e89-a00f-a2e6-aa8e2e1f3fce@web.de> (raw)
In-Reply-To: <20200527075715.36849-1-qiang.zhang@windriver.com>
> Thus delete this function call which became unnecessary with the referenced
> software update.
…
> Suggested-by: Markus Elfring <Markus.Elfring@web.de>
Would the tag “Co-developed-by” be more appropriate according to the patch review
to achieve a more pleasing commit message?
> v1->v2->v3->v4->v5:
> Modify weakly submitted information.
Now I wonder about your wording choice “weakly”.
Regards,
Markus
next prev parent reply other threads:[~2020-05-27 8:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 7:57 qiang.zhang
2020-05-27 8:20 ` Markus Elfring [this message]
[not found] ` <DM6PR11MB32573F3884A864ECD586235EFF8E0@DM6PR11MB3257.namprd11.prod.outlook.com>
2020-05-28 1:44 ` 回复: " Zhang, Qiang
2020-05-28 9:57 ` Dan Carpenter
2020-05-28 10:38 ` Tejun Heo
2020-05-28 11:00 ` [v5] " Markus Elfring
2020-05-28 14:40 ` Markus Elfring
2020-05-28 12:08 ` 回复: [PATCH v5] " Lai Jiangshan
2020-05-28 12:25 ` Dan Carpenter
2020-05-28 13:27 ` Lai Jiangshan
2020-05-28 14:03 ` Tejun Heo
2020-05-28 14:45 ` [v5] " Markus Elfring
2020-05-28 14:06 ` 回复: [PATCH v5] " Dan Carpenter
2020-05-28 15:25 ` [v5] " Markus Elfring
2020-05-28 15:02 ` Markus Elfring
2020-05-28 15:02 ` Markus Elfring
2020-05-27 13:52 ` [PATCH v5] " Tejun Heo
2020-05-28 1:29 qiang.zhang
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=284c7851-4e89-a00f-a2e6-aa8e2e1f3fce@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
Powered by JetHome