mirror of https://lore.kernel.org/lkml/
 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 bug fixes for 5.6
Date: Mon, 10 Feb 2020 18:18:36 -0600	[thread overview]
Message-ID: <20200211001836.GI7842@minyard.net> (raw)

The following changes since commit 6794862a16ef41f753abd75c03a152836e4c8028:

  Merge tag 'for-5.5-rc1-kconfig-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux (2019-12-09 12:14:31 -0800)

are available in the Git repository at:

  https://github.com/cminyard/linux-ipmi.git tags/for-linus-5.6-1

for you to fetch changes up to e0354d147e5889b5faa12e64fa38187aed39aad4:

  drivers: ipmi: fix off-by-one bounds check that leads to a out-of-bounds write (2020-01-20 11:01:00 -0600)

----------------------------------------------------------------
Minor bug fixes for IPMI

I know this is late; I've been travelling and, well, I've been
distracted.

This is just a few bug fixes and adding i2c support to the IPMB driver,
which is something I wanted from the beginning for it.  It would be
nice for the people doing IPMB to get this in.

-corey

----------------------------------------------------------------
Colin Ian King (1):
      drivers: ipmi: fix off-by-one bounds check that leads to a out-of-bounds write

Corey Minyard (1):
      ipmi:ssif: Handle a possible NULL pointer reference

Vijay Khemka (2):
      drivers: ipmi: Support raw i2c packet in IPMB
      drivers: ipmi: Modify max length of IPMB packet

 Documentation/driver-api/ipmb.rst |  4 ++++
 drivers/char/ipmi/ipmb_dev_int.c  | 33 +++++++++++++++++++++++++++++++--
 drivers/char/ipmi/ipmi_ssif.c     | 10 +++++++---
 3 files changed, 42 insertions(+), 5 deletions(-)


             reply	other threads:[~2020-02-11  0:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11  0:18 Corey Minyard [this message]
2020-02-16 21:10 ` 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=20200211001836.GI7842@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

Powered by JetHome