From: Dominique Martinet <dominique.martinet@atmark-techno.com>
To: Lino Sanfilippo <LinoSanfilippo@gmx.de>, Lukas Wunner <lukas@wunner.de>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
stable@vger.kernel.org,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Matthias Schiffer" <matthias.schiffer@ew.tq-group.com>,
"Roosen Henri" <Henri.Roosen@ginzinger.com>,
linux-serial@vger.kernel.org,
"Daisuke Mizobuchi" <mizo@atmark-techno.com>
Subject: Re: [PATCH 5.10 v2 1/2] serial: core: move RS485 configuration tasks from drivers into core
Date: Sat, 29 Oct 2022 15:58:55 +0900 [thread overview]
Message-ID: <Y1zPL0Y6bmqvvhMw@atmark-techno.com> (raw)
In-Reply-To: <4ff347e8-1ef4-e006-01db-3d420213f6e3@gmx.de>
Lino Sanfilippo wrote on Fri, Oct 28, 2022 at 10:06:51AM +0200:
> > I'd really appreciate if Lino could take a look and confirm we didn't
> > botch this too much -- we've tested the 5.10 version and it looks ok,
> > but this is different enough from the original patch to warrant a check
> > from the author.
>
> However the part Lukas authored (patch 2) seems to be the one that has been adjusted
> a lot, so maybe you rather/also want to have his ack?
Gah, sorry -- I'm juggling with too many things at once here and got the
two patches mixed up.
Yes, I meant Lukas here for patch 2/2, sorry. Promoted him to To.
And thank you Lino for having a look and pointing it out!
--
Dominique
prev parent reply other threads:[~2022-10-29 6:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 5:17 [PATCH 5.10 v2 1/2] serial: core: move RS485 configuration tasks from drivers into core Dominique Martinet
2022-10-17 5:17 ` [PATCH 5.10 v2 2/2] serial: Deassert Transmit Enable on probe in driver-specific way Dominique Martinet
2022-10-26 16:54 ` [PATCH 5.10 v2 1/2] serial: core: move RS485 configuration tasks from drivers into core Greg Kroah-Hartman
2022-10-27 0:21 ` Dominique Martinet
2022-10-27 10:24 ` Greg Kroah-Hartman
2022-10-28 8:06 ` Lino Sanfilippo
2022-10-29 6:58 ` Dominique Martinet [this message]
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=Y1zPL0Y6bmqvvhMw@atmark-techno.com \
--to=dominique.martinet@atmark-techno.com \
--cc=Henri.Roosen@ginzinger.com \
--cc=LinoSanfilippo@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-serial@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=mizo@atmark-techno.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.