From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dawei Li <dawei.li@shingroup.cn>
Cc: "Ilpo J�rvinen" <ilpo.jarvinen@linux.intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
jszhang@kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-serial <linux-serial@vger.kernel.org>,
set_pte_at@outlook.com, stable@kernel.org
Subject: Re: [PATCH] serial: dw8250: Make DLF feature independent of ADDITIONAL_FEATURE
Date: Tue, 5 Dec 2023 17:55:45 +0200 [thread overview]
Message-ID: <ZW9IASqCQi_Qi4UB@smile.fi.intel.com> (raw)
In-Reply-To: <6863B74199951BD2+ZW6DIO1n0phYBjg9@centos8>
On Tue, Dec 05, 2023 at 09:55:44AM +0800, Dawei Li wrote:
> On Mon, Dec 04, 2023 at 03:29:35PM +0200, Andy Shevchenko wrote:
> > On Mon, Dec 04, 2023 at 03:20:09PM +0200, Ilpo Järvinen wrote:
> > > On Mon, 4 Dec 2023, Dawei Li wrote:
...
> > > The very same code change is already in tty-next (from another author).
> >
> > For your convenience:
> >
> > d804987153e7 ("serial: 8250_dw: Decouple DLF register check from UCV")
>
> [sigh]
>
> Apparently I thought tty/for-linus is the "bug fixing" branch for tty by
> mistake, and didn't realize the same fix patch has been landed in tty-next
> for a while.
>
> Thanks for the update.
>
> Anyway, I believe the fixing patch should cc stable and be getting backported?
> I hit the bug on 5.10.x, it's possible the bug has been there before that.
When that commit meets upstream you can always resend it for stable. The process
is documented.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-12-05 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 13:08 [PATCH] serial: dw8250: Make DLF feature independent of ADDITIONAL_FEATURE Dawei Li
2023-12-04 13:20 ` Ilpo Järvinen
2023-12-04 13:29 ` Andy Shevchenko
2023-12-05 1:55 ` Dawei Li
2023-12-05 15:55 ` Andy Shevchenko [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=ZW9IASqCQi_Qi4UB@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dawei.li@shingroup.cn \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=set_pte_at@outlook.com \
--cc=stable@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