linux-serial.vger.kernel.org archive mirror
 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 fixes for 5.5-rc6
Date: Fri, 10 Jan 2020 22:08:35 +0100	[thread overview]
Message-ID: <20200110210835.GA1871048@kroah.com> (raw)

The following changes since commit 46cf053efec6a3a5f343fead837777efe8252a46:

  Linux 5.5-rc3 (2019-12-22 17:02:23 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tags/tty-5.5-rc6

for you to fetch changes up to c5ee0b3104e0b292d353e63fd31cb8c692645d8c:

  serdev: Don't claim unsupported ACPI serial devices (2020-01-06 20:00:44 +0100)

----------------------------------------------------------------
TTY/Serial fixes for 5.5-rc6

Here are two tty/serial driver fixes for 5.5-rc6.

The first fixes a much much reported issue with a previous tty port link
patch that is in your tree, and the second fixes a problem where the
serdev driver would claim ACPI devices that it shouldn't be claiming.

Both have been in linux-next for a while with no reported issues.

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

----------------------------------------------------------------
Punit Agrawal (1):
      serdev: Don't claim unsupported ACPI serial devices

Sudip Mukherjee (1):
      tty: always relink the port

 drivers/tty/serdev/core.c | 10 ++++++++++
 drivers/tty/tty_port.c    |  3 +--
 2 files changed, 11 insertions(+), 2 deletions(-)

             reply	other threads:[~2020-01-10 21:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 21:08 Greg KH [this message]
2020-01-11 14:45 ` [GIT PULL] TTY/Serial driver fixes for 5.5-rc6 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=20200110210835.GA1871048@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;
as well as URLs for NNTP newsgroup(s).