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: Wed, 18 Mar 2026 08:42:57 +0100	[thread overview]
Message-ID: <abpXgSLJ6s_JJ4lJ@hovoldconsulting.com> (raw)
In-Reply-To: <fa0765de-68cb-4bac-b7d7-e2b47946aac1@fintek.com.tw>

Hi Peter,

On Wed, Mar 18, 2026 at 08:46:28AM +0800, PS10 PETER HONG 洪繼澤 wrote:
> Johan Hovold 於 2026/3/17 下午 03:22 寫道:
> > On Tue, Mar 17, 2026 at 10:21:17AM +0800, PS10 PETER HONG 洪繼澤 wrote:

> >> 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.

> Typical users are unlikely to encounter this, but one of our customers is
> currently facing the issue. They have requested that we submit this patch to
> the stable tree so they can utilize the mainstream driver without needing a
> separate vendor driver.
> 
> In theory, applying this patch will improve the product's overall stability.
> We would like to see this integrated into the mainstream kernel tree.

Sounds good.

Johan

      reply	other threads:[~2026-03-18  7:43 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
2026-03-18  0:46   ` PS10 PETER HONG 洪繼澤
2026-03-18  7:42     ` Johan Hovold [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=abpXgSLJ6s_JJ4lJ@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