From: "Pali Rohár" <pali@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Allen Yan" <yanwei@marvell.com>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Gregory CLEMENT" <gregory.clement@bootlin.com>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] serial: mvebu: Apply old baudrate to termios
Date: Thu, 30 Jun 2022 10:28:49 +0200 [thread overview]
Message-ID: <20220630082849.ldvqu7frdrln4ite@pali> (raw)
In-Reply-To: <CAHp75VfDA1x0OQjBb8rj7RB9bHgjXa86jrcayeuxbYxGLf2=Kg@mail.gmail.com>
On Tuesday 28 June 2022 13:40:28 Andy Shevchenko wrote:
> On Tue, Jun 28, 2022 at 1:39 PM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
> > On Tue, Jun 28, 2022 at 12:01 PM Pali Rohár <pali@kernel.org> wrote:
> > > On Tuesday 28 June 2022 11:51:36 Pali Rohár wrote:
>
> ...
>
> > > Ou, now I see where is the issue. Patch which I tested and which fixes
> > > reporting baudrate is not in kernel tree yet and it looks like I totally
> > > forgot to sent it to ML. I will send it. Sorry for confusion.
> >
> > Shouldn't the Ilpo's applied anyway to fix the current code base?
>
> Ah, now I understand that your patch is a fix. Sorry for the noise.
Yes, my patch fixes the issue which Ilpo described and handles also errors:
https://lore.kernel.org/linux-serial/20220628100922.10717-1-pali@kernel.org/
prev parent reply other threads:[~2022-06-30 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 9:41 [PATCH] serial: mvebu: Apply old baudrate to termios Ilpo Järvinen
2022-06-28 9:51 ` Pali Rohár
2022-06-28 9:59 ` Pali Rohár
2022-06-28 11:39 ` Andy Shevchenko
2022-06-28 11:40 ` Andy Shevchenko
2022-06-30 8:28 ` Pali Rohár [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=20220630082849.ldvqu7frdrln4ite@pali \
--to=pali@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.clement@bootlin.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=yanwei@marvell.com \
/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).