The Linux Kernel Mailing List
 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 and additions for 6.2
Date: Tue, 13 Dec 2022 08:20:52 -0600	[thread overview]
Message-ID: <Y5iKRKVS+o7I3OL3@minyard.net> (raw)

The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:

  Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)

are available in the Git repository at:

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

for you to fetch changes up to c6f613e5f35b0e2154d5ca12f0e8e0be0c19be9a:

  ipmi/watchdog: use strscpy() to instead of strncpy() (2022-12-05 06:50:09 -0600)

----------------------------------------------------------------
Small fixes, a new SSIF i2c BMC-side interface

This includes a number of small fixes, as usual.

It also includes a new driver for doing the i2c (SSIF) interface
BMC-side, pretty much completing the BMC side interfaces.

----------------------------------------------------------------
Andrew Jeffery (1):
      ipmi: kcs: Poll OBF briefly to reduce OBE latency

Bo Liu (1):
      ipmi: Fix some kernel-doc warnings

Christophe JAILLET (1):
      ipmi/watchdog: Include <linux/kstrtox.h> when appropriate

Corey Minyard (1):
      ipmi:ssif: Increase the message retry time

Dan Carpenter (1):
      ipmi: fix use after free in _ipmi_destroy_user()

Quan Nguyen (3):
      ipmi: ssif_bmc: Add SSIF BMC driver
      bindings: ipmi: Add binding for SSIF BMC driver
      ipmi: ssif_bmc: Use EPOLLIN instead of POLLIN

Uwe Kleine-König (1):
      ipmi: ssif_bmc: Convert to i2c's .probe_new()

Zhang Yuchen (3):
      ipmi: fix long wait in unload when IPMI disconnect
      ipmi: fix memleak when unload ipmi driver
      ipmi: fix msg stack when IPMI is disconnected

yang.yang29@zte.com.cn (1):
      ipmi/watchdog: use strscpy() to instead of strncpy()

 .../devicetree/bindings/ipmi/ssif-bmc.yaml         |  38 +
 drivers/char/ipmi/Kconfig                          |  10 +
 drivers/char/ipmi/Makefile                         |   1 +
 drivers/char/ipmi/ipmi_kcs_sm.c                    |  16 +-
 drivers/char/ipmi/ipmi_msghandler.c                |  14 +-
 drivers/char/ipmi/ipmi_si_intf.c                   |  27 +-
 drivers/char/ipmi/ipmi_ssif.c                      |   2 +-
 drivers/char/ipmi/ipmi_watchdog.c                  |   4 +-
 drivers/char/ipmi/kcs_bmc_aspeed.c                 |  24 +-
 drivers/char/ipmi/ssif_bmc.c                       | 873 +++++++++++++++++++++
 include/uapi/linux/ipmi_ssif_bmc.h                 |  18 +
 11 files changed, 1004 insertions(+), 23 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/ipmi/ssif-bmc.yaml
 create mode 100644 drivers/char/ipmi/ssif_bmc.c
 create mode 100644 include/uapi/linux/ipmi_ssif_bmc.h


             reply	other threads:[~2022-12-13 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 14:20 Corey Minyard [this message]
2022-12-13 21:54 ` [GIT PULL] IPMI bug fixes and additions for 6.2 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=Y5iKRKVS+o7I3OL3@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