From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: ruihongluo <colorsu1922@gmail.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
"Jiri Slaby" <jirislaby@kernel.org>,
ruihongluo <luoruihong@xiaomi.com>
Subject: Re: [PATCH v1 1/1] serial: 8250: Preserve original value of DLF register
Date: Thu, 29 Jun 2023 12:20:37 +0300 [thread overview]
Message-ID: <ZJ1M5QvyWzgWNlpE@smile.fi.intel.com> (raw)
In-Reply-To: <20230628152135.56286-1-luoruihong@xiaomi.com>
On Wed, Jun 28, 2023 at 11:21:37PM +0800, ruihongluo wrote:
> This commit is aimed at preserving the original value of the
"This commit is aimed at preserving the original..." -->
"Preserve the original..."
> DLF(Divisor Latch Fraction Register). When the DLF register is
> modified without preservation, it can disrupt the baudrate settings
> established by firmware or bootloader , leading to data corruption
> and the generation of unreadable or distorted characters.
You have From different to SoB. You need to fix this.
It can be done by setting corresponding values in the ~/.gitconfig
of your machine where you are making patches on.
Quick fix is to run
git commit --amend --author="ruihongluo <luoruihong@xiaomi.com>"
and resend as a v2.
Code wise looks good to me, thank you for fixing this.
Perhaps it needs a Fixes tag, as
Fixes: 701c5e73b296 ("serial: 8250_dw: add fractional divisor support")
added before your SoB line. (Again, use `git commit --amend` to address
this.)
> Signed-off-by: ruihongluo <luoruihong@xiaomi.com>
> ---
Also don't forget to add a changelog here for v2 to describe your changes.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-06-29 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 15:21 [PATCH v1 1/1] serial: 8250: Preserve original value of DLF register ruihongluo
2023-06-29 9:20 ` Andy Shevchenko [this message]
2023-06-29 9:42 ` [PATCH v2 " ruihongluo
2023-06-29 11:06 ` Andy Shevchenko
2023-06-29 12:35 ` [PATCH v2] " Ruihong Luo
2023-06-29 13:06 ` Andy Shevchenko
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=ZJ1M5QvyWzgWNlpE@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=colorsu1922@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=luoruihong@xiaomi.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