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 fixes for 5.17-rc2
Date: Sat, 29 Jan 2022 14:12:14 +0100 [thread overview]
Message-ID: <YfU9LsK5kzsyBmRH@kroah.com> (raw)
The following changes since commit c2c94b3b187dc92b2002809f489e0f24a41e91bc:
Merge tag 'drm-next-2022-01-21' of git://anongit.freedesktop.org/drm/drm (2022-01-21 09:25:38 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git tags/char-misc-5.17-rc2
for you to fetch changes up to fc55e63e148f1db2180867da875460a00aac8bd1:
counter: fix an IS_ERR() vs NULL bug (2022-01-26 19:40:33 +0100)
----------------------------------------------------------------
Char/Misc driver fixes for 5.17-rc2
Here are two small char/misc driver fixes for 5.17-rc2 that fix some
reported issues. They include:
- fix up a merge issue in the at25.c driver that ended up
dropping some lines in the driver. The removed lines ended
being needed, so this restores it and the driver works again.
- counter core fix where the wrong error was being returned,
NULL should be the correct error for when memory is gone here,
like the kmalloc() core does.
Both of these have been in linux-next this week with no reported issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Dan Carpenter (1):
counter: fix an IS_ERR() vs NULL bug
Kees Cook (1):
eeprom: at25: Restore missing allocation
drivers/counter/counter-core.c | 15 ++++++---------
drivers/misc/eeprom/at25.c | 4 ++++
2 files changed, 10 insertions(+), 9 deletions(-)
next reply other threads:[~2022-01-29 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 13:12 Greg KH [this message]
2022-01-29 13:54 ` 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=YfU9LsK5kzsyBmRH@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®