From: Thomas Gleixner <tglx@linutronix.de>
To: Pan Chuang <panchuang@vivo.com>
Cc: linux-kernel@vger.kernel.org, miquel.raynal@bootlin.com,
Jonathan.Cameron@Huawei.com, u.kleine-koenig@pengutronix.de,
angeg.delregno@collabora.com, krzk@kernel.org,
a.fatoum@pengutronix.de, frank.li@vivo.com,
Pan Chuang <panchuang@vivo.com>
Subject: Re: [PATCH v8 1/1] genirq/devres: Add dev_err_probe() in devm_request_threaded_irq() and devm_request_any_context_irq()
Date: Tue, 29 Jul 2025 14:12:20 +0200 [thread overview]
Message-ID: <87ikjbjivv.ffs@tglx> (raw)
In-Reply-To: <20250729114804.21984-1-panchuang@vivo.com>
On Tue, Jul 29 2025 at 19:48, Pan Chuang wrote:
> On Tue, Jul 29 2025 at 17:14, Thomas Gleixner wrote:
>>> Signed-off-by: Yangtao Li <frank.li@vivo.com>
>>> Signed-off-by: Pan Chuang <panchuang@vivo.com>
>> This SOB chain is still incorrect. Again:
>>
>> https://www.kernel.org/doc/html/latest/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by
>>
>> If anything is unclear, then please ask.
>
> Could you please advise if this SOB chain is correct:
>
> Co-developed-by: Yangtao Li <frank.li@vivo.com>
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> Signed-off-by: Pan Chuang <panchuang@vivo.com>
If you are supposed to be listed as author of the patch in git, then
yes.
next prev parent reply other threads:[~2025-07-29 12:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 8:14 [PATCH v8 0/1] genirq/devres: Add dev_err_probe() in devm_request_threaded_irq() and devm_request_any_context_irq() Pan Chuang
2025-07-29 8:14 ` [PATCH v8 1/1] " Pan Chuang
2025-07-29 8:20 ` Ahmad Fatoum
2025-07-29 9:15 ` Thomas Gleixner
2025-07-29 9:14 ` Thomas Gleixner
2025-07-29 11:48 ` Pan Chuang
2025-07-29 12:12 ` Thomas Gleixner [this message]
2025-07-29 18:35 ` [PATCH v8 0/1] " Markus Elfring
2025-07-30 6:11 ` Pan Chuang
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=87ikjbjivv.ffs@tglx \
--to=tglx@linutronix.de \
--cc=Jonathan.Cameron@Huawei.com \
--cc=a.fatoum@pengutronix.de \
--cc=angeg.delregno@collabora.com \
--cc=frank.li@vivo.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=panchuang@vivo.com \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.