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 bug fixes for 6.3
Date: Wed, 22 Feb 2023 06:40:29 -0600	[thread overview]
Message-ID: <Y/YNPWfyZE4KteG2@minyard.net> (raw)

The following changes since commit 041fae9c105ae342a4245cf1e0dc56a23fbb9d3c:

  Merge tag 'f2fs-for-6.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs (2022-12-14 15:27:57 -0800)

are available in the Git repository at:

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

for you to fetch changes up to befb28f2676a65a5a4cc4626ae224461d8785af6:

  ipmi: ipmb: Fix the MODULE_PARM_DESC associated to 'retry_time_ms' (2023-02-10 07:38:18 -0600)

----------------------------------------------------------------
Small fixes to the SMBus IPMI and IPMB driver

Nothing big, cleanups, fixing names, and one small deviation from the
specification fixed.

----------------------------------------------------------------
Christophe JAILLET (1):
      ipmi: ipmb: Fix the MODULE_PARM_DESC associated to 'retry_time_ms'

Corey Minyard (4):
      ipmi:ssif: resend_msg() cannot fail
      ipmi_ssif: Rename idle state and check
      ipmi:ssif: Remove rtc_us_timer
      ipmi:ssif: Add a timer between request retries

 drivers/char/ipmi/ipmi_ipmb.c |   2 +-
 drivers/char/ipmi/ipmi_ssif.c | 113 ++++++++++++++++++++----------------------
 2 files changed, 56 insertions(+), 59 deletions(-)


             reply	other threads:[~2023-02-22 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 12:40 Corey Minyard [this message]
2023-02-22 19:53 ` [GIT PULL] IPMI bug fixes for 6.3 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=Y/YNPWfyZE4KteG2@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