public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: 240401736@qq.com
Cc: andriy.shevchenko@linux.intel.com, ilpo.jarvinen@linux.intel.com,
	jirislaby@kernel.org, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org, ??? <luoruihong@xiaomi.com>,
	??? <weipengliang@xiaomi.com>, ??? <wengjinfei@xiaomi.com>,
	colorsu1922@gmail.com
Subject: Re: [PATCH v2] serial: 8250: Preserve original value of DLF register
Date: Wed, 9 Aug 2023 13:47:07 +0200	[thread overview]
Message-ID: <2023080954-everyday-galore-f520@gregkh> (raw)
In-Reply-To: <tencent_CE78164E0DD743EAA6FD70A1D7F8565F9609@qq.com>

On Wed, Aug 09, 2023 at 02:30:58PM +0800, 240401736@qq.com wrote:
> On Thu, 29 Jun 2023 20:35:30 +0800, ruihongluo wrote:
> > This commit is aimed at preserving the original value of the
> > 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.
> >
> > Fixes: 701c5e73b296 ("serial: 8250_dw: add fractional divisor support")
> > Signed-off-by: Ruihong Luo <luoruihong@xiaomi.com>
> 
> Will this patch be merged into the 5.15 branch? We also need this patch on
> the 5.15 branch.

What is the git commit id of it in Linus's tree?

thanks,

greg k-h

       reply	other threads:[~2023-08-09 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_CE78164E0DD743EAA6FD70A1D7F8565F9609@qq.com>
2023-08-09 11:47 ` Greg KH [this message]
2023-06-29 11:06 [PATCH v2 1/1] serial: 8250: Preserve original value of DLF register 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=2023080954-everyday-galore-f520@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=240401736@qq.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=colorsu1922@gmail.com \
    --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 \
    --cc=weipengliang@xiaomi.com \
    --cc=wengjinfei@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