From: Thomas Gleixner <tglx@linutronix.de>
To: markus.stockhausen@gmx.de, tsbogend@alpha.franken.de,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
s.gottschall@dd-wrt.com
Subject: Re: AW: [PATCH v2] irqchip/mips-gic: allow forced affinity
Date: Fri, 20 Jun 2025 17:49:31 +0200 [thread overview]
Message-ID: <87cyayqupg.ffs@tglx> (raw)
In-Reply-To: <25e101dbdc24$fb5cd4e0$f2167ea0$@gmx.de>
On Fri, Jun 13 2025 at 07:35, markus stockhausen wrote:
>> Von: Thomas Gleixner <tglx@linutronix.de>
>> Gesendet: Donnerstag, 12. Juni 2025 15:14
>>
>> On Mon, May 26 2025 at 09:41, Markus Stockhausen wrote:
>> >
>> > Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
>> > Signed-off-by: Sebastian Gottschall <s.gottschall@dd-wrt.com>
>>
>> This Signed-off-by chain is broken.
>>
>>
> https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-
> your-work-the-developer-s-certificate-of-origin
>>
>> and the following paragraphs explain it.
>
> This is my first co-authorship. So want to make sure that I understand it
> correctly.
>
> - I developed the patched and
> - Sebastian gave helpful input for it.
>
> So it should be like this?
>
> Co-developed-by: Sebastian Gottschall <s.gottschall@dd-wrt.com>
> Signed-off-by: Sebastian Gottschall <s.gottschall@dd-wrt.com>
> Signed-off-by: Markus Stockhausen <markus.stockhausen@gmx.de>
Yes.
prev parent reply other threads:[~2025-06-20 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 13:41 [PATCH v2] irqchip/mips-gic: allow forced affinity Markus Stockhausen
2025-06-12 13:13 ` Thomas Gleixner
2025-06-13 5:35 ` AW: " markus.stockhausen
2025-06-20 15:49 ` Thomas Gleixner [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=87cyayqupg.ffs@tglx \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=markus.stockhausen@gmx.de \
--cc=s.gottschall@dd-wrt.com \
--cc=tsbogend@alpha.franken.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox