All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] Char/Misc driver fix for 5.6-rc1
Date: Mon, 3 Feb 2020 14:39:39 +0000	[thread overview]
Message-ID: <20200203143939.GA3221812@kroah.com> (raw)

The following changes since commit 15d6632496537fa66488221ee5dd2f9fb318ef2e:

  Merge branch 'urgent-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu (2020-01-29 11:04:49 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git tags/char-misc-5.6-rc1-2

for you to fetch changes up to 98c49f1746ac44ccc164e914b9a44183fad09f51:

  char: hpet: Fix out-of-bounds read bug (2020-01-30 06:58:33 +0100)

----------------------------------------------------------------
Char/Misc fix for 5.6-rc1

Here is a single patch, that fixes up a commit that came in the previous
char/misc merge.

It fixes a bug in the hpet driver that everyone keeps tripping over in
their automated testing.  Good thing is, people are catching it.  Bad
thing it wasn't caught by anyone testing before this.  Oh well...

This has been in linux-next for a few days with no reported issues.

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

----------------------------------------------------------------
Gustavo A. R. Silva (1):
      char: hpet: Fix out-of-bounds read bug

 drivers/char/hpet.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

             reply	other threads:[~2020-02-03 14:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03 14:39 Greg KH [this message]
2020-02-03 15:15 ` [GIT PULL] Char/Misc driver fix for 5.6-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=20200203143939.GA3221812@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.