From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: Jiri Slaby <jslaby@suse.com>,
"Matwey V. Kornilov" <matwey@sai.msu.ru>,
Heiko Schocher <hs@denx.de>,
Giulio Benetti <giulio.benetti@micronovasrl.com>,
Uwe Kleine-Koenig <u.kleine-koenig@pengutronix.de>,
Stefan Wahren <wahrenst@gmx.net>,
Martin Sperl <kernel@martin.sperl.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH tty-next 1/2] serial: 8250: Fix rs485 delay after console write
Date: Thu, 26 Mar 2020 15:40:47 +0100 [thread overview]
Message-ID: <20200326144047.GA1403361@kroah.com> (raw)
In-Reply-To: <b420d9c3b1c8b0492db55cc6f62076bfd9968b2f.1585224378.git.lukas@wunner.de>
On Thu, Mar 26, 2020 at 01:20:15PM +0100, Lukas Wunner wrote:
> Due to a silly copy-paste mistake, commit 6194c38fc20d ("serial: 8250:
> Support console on software emulated rs485 ports") erroneously pauses
> for the duration of delay_rts_before_send after writing to the console,
> instead of delay_rts_after_send. Mea culpa.
>
> Fixes: 6194c38fc20d ("serial: 8250: Support console on software emulated rs485 ports")
Where did this commit id come from?
Don't you mean 7f9803072ff6 ("serial: 8250: Support console on software
emulated rs485 ports")?
If so, can you please fix this up and resend the series?
thanks,
greg k-h
next prev parent reply other threads:[~2020-03-26 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 12:20 [PATCH tty-next 1/2] serial: 8250: Fix rs485 delay after console write Lukas Wunner
2020-03-26 12:20 ` [PATCH tty-next 2/2] serial: 8250: Optimize irq enable " Lukas Wunner
2020-03-26 14:40 ` Greg Kroah-Hartman [this message]
2020-03-26 15:05 ` [PATCH tty-next 1/2] serial: 8250: Fix rs485 delay " Lukas Wunner
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=20200326144047.GA1403361@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=giulio.benetti@micronovasrl.com \
--cc=heiko@sntech.de \
--cc=hs@denx.de \
--cc=jslaby@suse.com \
--cc=kernel@martin.sperl.org \
--cc=linux-serial@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=matwey@sai.msu.ru \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wahrenst@gmx.net \
/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).