public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: [GIT PULL] TTY / Serial driver fix for 6.18-rc1
Date: Tue, 7 Oct 2025 15:08:36 +0200	[thread overview]
Message-ID: <aOUQ1CdKRQ2mSN1f@kroah.com> (raw)

The following changes since commit f83ec76bf285bea5727f478a68b894f5543ca76e:

  Linux 6.17-rc6 (2025-09-14 14:21:14 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tags/tty-6.18-rc1

for you to fetch changes up to a699213d4e6ef4286348c6439837990f121e0c03:

  serial: qcom-geni: Fix blocked task (2025-09-17 13:12:17 +0200)

----------------------------------------------------------------
TTY driver fix for 6.18-rc1

Here is a single driver fix for the qcom_geni_serial driver for
6.18-rc1.  It has been in my tree for weeks, but missed being sent to
you for 6.17-final due to travel on my side.

This fixes a reported regression for this driver that prevents 6.17 from
working properly on this platform.

It has been in linux-next for many weeks with no reported issues.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Krzysztof Kozlowski (1):
      serial: qcom-geni: Fix blocked task

 drivers/tty/serial/qcom_geni_serial.c | 176 ++++------------------------------
 1 file changed, 16 insertions(+), 160 deletions(-)

             reply	other threads:[~2025-10-07 13:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07 13:08 Greg KH [this message]
2025-10-07 19:46 ` [GIT PULL] TTY / Serial driver fix for 6.18-rc1 pr-tracker-bot

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=aOUQ1CdKRQ2mSN1f@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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