[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240517092250.33314-1-kuniyu@amazon.com>
Date: Fri, 17 May 2024 18:22:50 +0900
From: Kuniyuki Iwashima <kuniyu@...zon.com>
To: <mhal@...x.co>
CC: <davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>,
<kuniyu@...zon.com>, <netdev@...r.kernel.org>, <pabeni@...hat.com>,
<shuah@...nel.org>
Subject: Re: [PATCH net v2 1/2] af_unix: Fix garbage collection of embryos carrying OOB with SCM_RIGHTS
From: Michal Luczaj <mhal@...x.co>
Date: Fri, 17 May 2024 10:55:53 +0200
> On 5/17/24 09:47, Kuniyuki Iwashima wrote:
> > From: Michal Luczaj <mhal@...x.co>
> > Date: Fri, 17 May 2024 07:59:16 +0200
> >> One question: git send-email automatically adds my Signed-off-by to your
> >> patch (patch 2/2 in this series). Should I leave it that way?
> >
> > SOB is usually added by someone who changed the diff or merged it.
> >
> > I think it would be better not to add it if not intended. At least
> > on my laptop, it does not add SOB automatically.
>
> Sure, I understand. And the problem was that I had format.signOff = true in
> .gitconfig. Fixed.
>
> > FWIW, my command is like
> >
> > git send-email --annotate --cover-letter --thread --no-chain-reply-to \
> > --subject-prefix "PATCH v1 net-next" \
>
> maintainer-netdev.rst shows an example with a slightly different order:
> "[PATCH net-next v3]". But I guess it doesn't matter?
It seems patchwork can parse either format. ("net,vX" and "vX,net")
https://patchwork.kernel.org/project/netdevbpf/list/
Powered by blists - more mailing lists