public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: "PS10 PETER HONG 洪繼澤" <peter_hong@fintek.com.tw>
Cc: gregkh@linuxfoundation.org, sashal@kernel.org, stable@vger.kernel.org
Subject: Re: Post-facto backport request: USB: serial: f81232: fix incomplete serial port generation
Date: Tue, 17 Mar 2026 08:22:56 +0100	[thread overview]
Message-ID: <abkBUCw0BTh4wfqs@hovoldconsulting.com> (raw)
In-Reply-To: <5bcf02b5-3fe5-466e-a1da-0e5a2e62fd5f@fintek.com.tw>

On Tue, Mar 17, 2026 at 10:21:17AM +0800, PS10 PETER HONG 洪繼澤 wrote:
> Hi Stable Team,
> 
> I would like to request a backport for the following commit to the
> currently supported stable trees 6.1.y, 6.6.y, 6.12.y and 6.18.y
> 
>    cd644b805da8 ("USB: serial: f81232: fix incomplete serial port 
> generation")
> 
> Reason:
>    This patch fixes a stability issue where Fintek F81532A/534A/535/536
>    devices fail to initialize all serial ports during fast load/unload 
> cycles.
>    The fix involves a dummy read to clear the device's stale internal state.
> 
> The patch should apply cleanly to most recent stable branches.

My understanding was that this was only something you'd hit if you
unload and reload the driver which isn't something a user would normally
do. That's why I didn't add a stable tag.

The diff is a bit on the bigger side but it's all straight-forward
enough so I'm fine with backporting if you think it will be useful also
for older kernels.

Johan

  reply	other threads:[~2026-03-17  7:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17  2:21 Post-facto backport request: USB: serial: f81232: fix incomplete serial port generation PS10 PETER HONG 洪繼澤
2026-03-17  7:22 ` Johan Hovold [this message]
2026-03-18  0:46   ` PS10 PETER HONG 洪繼澤
2026-03-18  7:42     ` Johan Hovold

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=abkBUCw0BTh4wfqs@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=peter_hong@fintek.com.tw \
    --cc=sashal@kernel.org \
    --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