[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200414175435.GF1011271@unreal>
Date: Tue, 14 Apr 2020 20:54:35 +0300
From: Leon Romanovsky <leon@...nel.org>
To: Borislav Petkov <bp@...e.de>
Cc: "David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Andy Gospodarek <andy@...yhouse.net>,
Ion Badulescu <ionut@...ula.org>,
Jay Vosburgh <j.vosburgh@...il.com>, linux-pm@...r.kernel.org,
netdev@...r.kernel.org, Pensando Drivers <drivers@...sando.io>,
Sebastian Reichel <sre@...nel.org>,
Shannon Nelson <snelson@...sando.io>,
Veaceslav Falico <vfalico@...il.com>
Subject: Re: [PATCH net-next 1/4] drivers: Remove inclusion of vermagic header
On Tue, Apr 14, 2020 at 07:44:32PM +0200, Borislav Petkov wrote:
> On Tue, Apr 14, 2020 at 08:26:04PM +0300, Leon Romanovsky wrote:
> > I personally don't use such notation and rely on the submission flow.
> >
> > The patch has two authors both written in SOBs and it will be visible
> > in the git history that those SOBs are not maintainers additions.
>
> A lonely SOB doesn't explain what the involvement of the person is. It
> is even documented:
>
> Documentation/process/submitting-patches.rst
>
> Section 12) When to use Acked-by:, Cc:, and Co-developed-by:
I know, and never liked that "Co-developed-by" tag and prefer
to be in old school camp who uses SOB to mark the author. :)
>
> I guess that is the maintainer of the respective tree's call in the end.
>
> > Can you please reply to the original patch with extra tags you want,
> > so b4 and patchworks will pick them without me resending the patches?
>
> Ok.
Thanks
>
> --
> Regards/Gruss,
> Boris.
>
> SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
Powered by blists - more mailing lists