From: Corey Minyard <corey@minyard.net>
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.17
Date: Wed, 6 Aug 2025 15:41:55 -0500 [thread overview]
Message-ID: <aJO-ExS1Zz-eMuZe@mail.minyard.net> (raw)
Something came in a bit late (the rate limiting patch) that I wanted to
get in, so I waited a bit with it in the next tree before requesting
a pull.
The following changes since commit cd2e103d57e5615f9bb027d772f93b9efd567224:
Merge tag 'hardening-v6.16-rc1-fix1-take2' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux (2025-06-01 11:37:01 -0700)
are available in the Git repository at:
https://github.com/cminyard/linux-ipmi.git tags/for-linus-6.17-1
for you to fetch changes up to ec50ec378e3fd83bde9b3d622ceac3509a60b6b5:
ipmi: Use dev_warn_ratelimited() for incorrect message warnings (2025-07-10 07:59:43 -0500)
----------------------------------------------------------------
Some small fixes for the IPMI driver
Nothing huge, some rate limiting on logs, a strncpy fix where the source
and destination could be the same, and removal of some unused cruft.
----------------------------------------------------------------
Breno Leitao (1):
ipmi: Use dev_warn_ratelimited() for incorrect message warnings
Colin Ian King (1):
char: ipmi: remove redundant variable 'type' and check
Corey Minyard (1):
ipmi: Fix strcpy source and destination the same
drivers/char/ipmi/ipmi_msghandler.c | 8 ++---
drivers/char/ipmi/ipmi_si_intf.c | 4 ---
drivers/char/ipmi/ipmi_watchdog.c | 59 ++++++++++++++++++++++++++-----------
3 files changed, 46 insertions(+), 25 deletions(-)
next reply other threads:[~2025-08-06 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 20:41 Corey Minyard [this message]
2025-08-07 5:30 ` [GIT PULL] IPMI bug fixes for 6.17 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=aJO-ExS1Zz-eMuZe@mail.minyard.net \
--to=corey@minyard.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.