public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	openipmi-developer@lists.sourceforge.net
Subject: [GIT PULL] IPMI serious bugfixes for 5.1
Date: Wed, 17 Apr 2019 10:46:54 -0500	[thread overview]
Message-ID: <20190417154654.GL4121@minyard.net> (raw)

The following changes since commit 444fe991353987c1c9bc5ab1f903d01f1b4ad415:

  Merge tag 'riscv-for-linus-5.1-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/palmer/riscv-linux (2019-04-16 10:46:37 -0700)

are available in the Git repository at:

  https://github.com/cminyard/linux-ipmi.git tags/for-linus-5.1-2

for you to fetch changes up to 3b9a907223d7f6b9d1dadea29436842ae9bcd76d:

  ipmi: fix sleep-in-atomic in free_user at cleanup SRCU user->release_barrier (2019-04-17 10:29:27 -0500)

----------------------------------------------------------------
Fixes for some bugs cause by recent changes.  One crash if you
feed bad data to the module parameters, one BUG that sometimes
occurs when a user closes the connection, and one bug that
cause the driver to not work if the configuration information
only comes in from SMBIOS.

----------------------------------------------------------------
Corey Minyard (2):
      ipmi: Fix failure on SMBIOS specified devices
      ipmi: fix sleep-in-atomic in free_user at cleanup SRCU user->release_barrier

Tony Camuso (1):
      ipmi: ipmi_si_hardcode.c: init si_type array to fix a crash

 drivers/char/ipmi/ipmi_dmi.c         |  1 -
 drivers/char/ipmi/ipmi_msghandler.c  | 19 +++++++++++++++++--
 drivers/char/ipmi/ipmi_si_hardcode.c |  2 ++
 3 files changed, 19 insertions(+), 3 deletions(-)


             reply	other threads:[~2019-04-17 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17 15:46 Corey Minyard [this message]
2019-04-17 17:50 ` [GIT PULL] IPMI serious bugfixes for 5.1 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=20190417154654.GL4121@minyard.net \
    --to=minyard@acm.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    --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