From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"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: Tue, 7 Jun 2022 12:32:29 +0200 [thread overview]
Message-ID: <20220607103229.f4hniwkcyfwlgem2@pengutronix.de> (raw)
In-Reply-To: <CAHp75VcUBOcz_UAx9tVER8cBb8h8NF+NivUH00-B39wwH6ObUQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2377 bytes --]
Hello,
On Tue, Jun 07, 2022 at 12:09:39PM +0200, Andy Shevchenko wrote:
> > > > > 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.
Reading that by the letter, it doesn't say you must not use Ack if there
is a S-o-b.
If a person was not directly involved in the preparation or
handling of a patch but wishes to signify and record their
approval of it then they can ask to have an Acked-by: line added
to the patch’s changelog.
It's "If" and not "Iff". Not sure if that is intended?!
> > That's unintuitive (and wrong) in my opinion.
>
> I have the opposite opinion.
>
> > For me, Acked-by is a
> > confirmation of the respective person, that the patch in question is ok.
> > If I take a hunk of a random reverted patch and add the S-o-b of the big
> > patch's author, can I really assume the original author "acks" the
> > result? I would expect that in most cases they don't. (And if they do,
> > there is no way to record it, because the usual way of adding an Ack is
> > blocked as there is already a S-o-b?)
>
> It's very logical to me. If you allowed (by not NAKing) the other
> developer to use your SoB you imply Ack for every change they made.
So you assume that you notice each patch with your S-o-b in time to send
a NAK. I don't claim that for me and I would be surprised if a major
part of the kernel contributors did.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-06-07 10:33 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
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 [this message]
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=20220607103229.f4hniwkcyfwlgem2@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=andy.shevchenko@gmail.com \
--cc=corbet@lwn.net \
--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 \
/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).