From: Michal Simek <michal.simek@xilinx.com>
To: Matt Redfearn <matt.redfearn@mips.com>,
Michal Simek <michal.simek@xilinx.com>,
linux-kernel@vger.kernel.org, monstr@monstr.eu
Cc: stable <stable@vger.kernel.org>, Jiri Slaby <jslaby@suse.com>,
Douglas Anderson <dianders@chromium.org>,
linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jeffy Chen <jeffy.chen@rock-chips.com>
Subject: Re: [PATCH] serial: 8250_early: Setup divider when uartclk is passed
Date: Tue, 24 Apr 2018 14:27:47 +0200 [thread overview]
Message-ID: <4e5e4f48-ec79-2c99-a321-83c0e383991a@xilinx.com> (raw)
In-Reply-To: <f8c69fee-8889-f0aa-1235-b7a65068238b@mips.com>
Hi Matt,
On 23.4.2018 15:21, Matt Redfearn wrote:
> Hi Michal
>
> On 23/04/18 10:18, Michal Simek wrote:
>> device->baud is always non zero value because it is checked already in
>> early_serial8250_setup() before init_port is called.
>
> True, currently init_port is only called from the one location and so
> the test is a little redundant, though I don't see the harm in testing
> both inputs to the divisor calculation immediately before use such that
> any future call path avoids setting a bad divisor.
I will let others to decide.
>
>>
>> Fixes: 0ff3ab701963 ("serial: 8250_early: Only set divisor if valid
>> clk & baud")
>> Cc: stable <stable@vger.kernel.org>
>
> Even if the test is dropped going forward, I wouldn't consider it's
> presence a "bug" such that a fix needs to be backported.
Not a problem with not adding this to stable.
Thanks,
Michal
next prev parent reply other threads:[~2018-04-24 12:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 9:18 [PATCH] serial: 8250_early: Setup divider when uartclk is passed Michal Simek
2018-04-23 13:21 ` Matt Redfearn
2018-04-24 12:27 ` Michal Simek [this message]
2018-04-25 12:51 ` Greg Kroah-Hartman
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=4e5e4f48-ec79-2c99-a321-83c0e383991a@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeffy.chen@rock-chips.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=matt.redfearn@mips.com \
--cc=monstr@monstr.eu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox