From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "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>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH v2 1/6] serial: 8250: Store to lsr_save_flags after lsr read
Date: Mon, 6 Jun 2022 19:52:19 +0300 (EEST) [thread overview]
Message-ID: <97e83f-8011-37fb-d958-2d881fcdbd3@linux.intel.com> (raw)
In-Reply-To: <CAHp75Ve4t1aF4wDpXPOcOX3MXbn_DaaNWG4S9Ft1jpZ0dGSXzw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
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:
> > On Mon, 6 Jun 2022, Ilpo Järvinen wrote:
>
> ...
>
> > > Fixes: e490c9144cfa ("tty: Add software emulated RS485 support for 8250")
> > > Link: https://lore.kernel.org/all/1d6c31d-d194-9e6a-ddf9-5f29af829f3@linux.intel.com/T/#m1737eef986bd20cf19593e344cebd7b0244945fc
> > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > > Acked-by: Uwe Kleine-König <u.kleine-koenig@penugtronix.de>
> >
> > It seems that Uwe managed to mistype his email for the A-by which I just
> > happily copy-pasted.
> >
> > Greg, please let me know if you want me to resend the series (or if you
> > will just change it on the fly while applying).
>
> I believe Greg doesn't handle patches on the fly, hence resend.
> 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.
next prev parent reply other threads:[~2022-06-06 17:17 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 ` 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 [this message]
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
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=97e83f-8011-37fb-d958-2d881fcdbd3@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®