From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Greg KH" <gregkh@linuxfoundation.org>,
linux-serial <linux-serial@vger.kernel.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Matwey V. Kornilov" <matwey@sai.msu.ru>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/6] serial: 8250: Store to lsr_save_flags after lsr read
Date: Mon, 6 Jun 2022 22:38:37 +0200 [thread overview]
Message-ID: <CAHp75VdiJFtLnEJfW6KXwaVFsKWSSTSMgKQLvikSEQj7x3tgLA@mail.gmail.com> (raw)
In-Reply-To: <20220606194046.gbt4ghz2yvazsfo4@pengutronix.de>
On Mon, Jun 6, 2022 at 9:40 PM Uwe Kleine-König
<u.kleine-koenig@pengutronix.de> wrote:
>
> On Mon, Jun 06, 2022 at 07:01:15PM +0200, Andy Shevchenko wrote:
> > On Mon, Jun 6, 2022 at 6:54 PM Ilpo Järvinen
> > <ilpo.jarvinen@linux.intel.com> wrote:
> > > On Mon, 6 Jun 2022, Andy Shevchenko wrote:
> > > > On Mon, Jun 6, 2022 at 3:55 PM Ilpo Järvinen
> > > > <ilpo.jarvinen@linux.intel.com> wrote:
> >
> > ...
> >
> > > > But more importantly I do not see the reason for the Acked-by tag when
> > > > SoB of the same person is present.
> > >
> > > I just repeated what Uwe gave me. Maybe he didn't notice he was already
> > > there as SoB.
> > >
> > > This situation is anyway a bit more complex than usual. The line I took
> > > was part of Uwe's much larger patch initially (which was fully reverted)
> > > so his SoB was carried over to preserve the authorship. As I made a
> > > non-trivial modification to his original patch by removing almost all of
> > > it, I added my SoB too. Given this situation, I kind of thought he Acked
> > > (approved) the post-modification version of it.
> >
> > I believe you haven't preserved the authorship that way (since From
> > line is different), but since you have done non-trivial changes and
> > Uwe is okay with them, the straightforward tag chain would be (with
> > your authorship implied):
> > Co-developed-by: Uwe
> > SoB: Uwe
> > SoB: yours
>
> I don't care much, but IMHO the initial set of tags made sense to me.
> It
> has my S-o-b because the change is (somewhat) taken from me and it has
> my ack because the modification looked good to me.
According to
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#when-to-use-acked-by-cc-and-co-developed-by
the SoB already implies that you developed that, but Ack if not. It
also clarifies Co-developed-by for cases like this.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-06-06 20:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220606131124.53394-1-ilpo.jarvinen@linux.intel.com>
2022-06-06 13:11 ` [PATCH v2 1/6] serial: 8250: Store to lsr_save_flags after lsr read Ilpo Järvinen
2022-06-06 13:41 ` Ilpo Järvinen
2022-06-06 14:09 ` Andy Shevchenko
2022-06-06 16:52 ` Ilpo Järvinen
2022-06-06 17:01 ` Andy Shevchenko
2022-06-06 19:40 ` Uwe Kleine-König
2022-06-06 20:38 ` Andy Shevchenko [this message]
2022-06-07 5:58 ` Uwe Kleine-König
2022-06-07 10:09 ` Andy Shevchenko
2022-06-07 10:32 ` Uwe Kleine-König
2022-06-07 10:54 ` Andy Shevchenko
2022-06-06 13:11 ` [PATCH v2 2/6] serial: 8250: Create serial_lsr_in() Ilpo Järvinen
2022-06-06 13:11 ` [PATCH v2 3/6] serial: 8250: Get preserved flags using serial_lsr_in() Ilpo Järvinen
2022-06-06 13:11 ` [PATCH v2 4/6] serial: 8250: Adjust misleading LSR related comment Ilpo Järvinen
2022-06-06 13:11 ` [PATCH v2 5/6] serial: 8250_dw: Use serial_lsr_in() in dw8250_handle_irq() Ilpo Järvinen
2022-06-06 13:11 ` [PATCH v2 6/6] serial: 8250_dw: Store LSR into lsr_saved_flags in dw8250_tx_wait_empty() Ilpo Järvinen
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=CAHp75VdiJFtLnEJfW6KXwaVFsKWSSTSMgKQLvikSEQj7x3tgLA@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=matwey@sai.msu.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).