linux-kernel.vger.kernel.org archive mirror
 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" 
	<openipmi-developer@lists.sourceforge.net>
Subject: Pull request for the IPMI driver for 4.0
Date: Fri, 10 Apr 2015 21:24:26 -0500	[thread overview]
Message-ID: <552885DA.8050909@acm.org> (raw)

The following changes since commit 3259b12ae1c79c146809829412ddc0d11a1b8e26:

  Merge tag 'scsi-fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi (2015-04-10
17:41:47 -0700)

are available in the git repository at:


  git://git.code.sf.net/p/openipmi/linux-ipmi tags/for-linus-4.0-1

for you to fetch changes up to d0acf734d886ce50bb5103cc75f7ca39f280e8a7:

  ipmi_ssif: Use interruptible completion for waiting in the thread
(2015-04-10 20:51:42 -0500)

----------------------------------------------------------------
Some annoying issues in the IPMI driver that would be good to have
fixed before 4.0 is released.

These got reported or discovered late, but they will avoid some situations
that would cause lots of log spam and in one case a deadlock.
----------------------------------------------------------------
Alistair Popple (1):
      ipmi/powernv: Fix minor locking bug

Corey Minyard (2):
      ipmi: Handle BMCs that don't allow clearing the rcv irq bit
      ipmi_ssif: Use interruptible completion for waiting in the thread

 drivers/char/ipmi/ipmi_powernv.c |   1 +
 drivers/char/ipmi/ipmi_si_intf.c | 109
++++++++++++++++++++++++++++++++++++---
 drivers/char/ipmi/ipmi_ssif.c    |   8 +--
 3 files changed, 108 insertions(+), 10 deletions(-)


                 reply	other threads:[~2015-04-11  2:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=552885DA.8050909@acm.org \
    --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;
as well as URLs for NNTP newsgroup(s).