mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Tomas Krcka <tomas.krcka@gmail.com>,
	linux-arm-kernel@lists.infradead.org,  nh-open-source@amazon.com,
	Tomas Krcka <krckatom@amazon.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Hagar Hemdan <hagarhem@amazon.com>,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irqchip/gic-v3-its: fix raw_local_irq_restore() called with IRQs enabled
Date: Mon, 30 Dec 2024 18:01:47 +0000	[thread overview]
Message-ID: <ef7592ced999db8f7affad6814e4bbfffe8d1853.camel@infradead.org> (raw)
In-Reply-To: <86frm5p06l.wl-maz@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2611 bytes --]

On Mon, 2024-12-30 at 17:09 +0000, Marc Zyngier wrote:
> On Mon, 30 Dec 2024 15:21:38 +0000,
> David Woodhouse <dwmw2@infradead.org> wrote:
> > 
> > [1  <text/plain; UTF-8 (quoted-printable)>]
> > On Mon, 2024-12-30 at 14:28 +0000, Marc Zyngier wrote:
> > > 
> > > Two problems here:
> > > 
> > > - there is no "From Tomas Krcka <krckatom@amazon.de>" at the beginning
> > >   of the patch, which is needed since you are posting from a gmail.com
> > >   address
> > > 
> > > - there is no SoB using your gmail.com address, which is needed since
> > >   this patch appears to be from your Amazon doppelganger.
> > 
> > The latter isn't needed if you have the former, surely?
> 
> I don't see why we shouldn't have it. AFAIC, this is a different
> sender, and I'm pretty sure tglx applies the same policy.

Not in my experience. I send patches like this all the time and don't
recall anyone ever complaining. People often have to work around broken
corporate email but still want to have the authorship correctly
attributed.

In the git log you can find plenty of commits containing
'Link:.*lore.kernel.org.*dwmw2@infradead.org' which I sent from my own
address, for which the Author and SoB are both @amazon.

Let's see if I can find a tglx one... 

https://lore.kernel.org/all/20240802135555.564941-2-dwmw2@infradead.org
which became https://git.kernel.org/torvalds/c/70e6b7d9ae3c6 for
example?

The point of the From: line at the top of the email body is to
*replace* the one in the header. Or put another way, the one in the
header is used as a fallback if there is no explicit From: in the body
of the message.

Documentation/process/submitting-patches.rst phrases it the second way:

The ``from`` line must be the very first line in the message body,
and has the form:

        From: Patch Author <author@example.com>

The ``from`` line specifies who will be credited as the author of the
patch in the permanent changelog.  If the ``from`` line is missing,
then the ``From:`` line from the email header will be used to determine
the patch author in the changelog.

> > I've lost count of the number of patches I've posted over the decades
> > from my function non-corporate email address, just using a From: and
> > Signed-off-by: in the body for my work address. We've always accepted
> > that, and git-am does the right thing (discarding the actual From:
> > address from the headers of the email).
> 
> Is that the royal 'We'?


Nah, it's been a while since I've been an active maintainer of anything
and applying patches from email. :)

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5069 bytes --]

      reply	other threads:[~2024-12-30 18:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-30 13:49 Tomas Krcka
2024-12-30 14:28 ` Marc Zyngier
2024-12-30 15:10   ` Krcka, Tomas
2024-12-30 15:21   ` David Woodhouse
2024-12-30 17:09     ` Marc Zyngier
2024-12-30 18:01       ` David Woodhouse [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=ef7592ced999db8f7affad6814e4bbfffe8d1853.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=hagarhem@amazon.com \
    --cc=krckatom@amazon.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=nh-open-source@amazon.com \
    --cc=tglx@linutronix.de \
    --cc=tomas.krcka@gmail.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

all inboxes | Powered by JetHome®