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.11
Date: Tue, 16 Jul 2024 08:28:21 -0500 [thread overview]
Message-ID: <ZpZ1dVeLWUbAd89V@mail.minyard.net> (raw)
The following changes since commit 0cac73eb3875f6ecb6105e533218dba1868d04c9:
Merge tag 'pm-6.10-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm (2024-06-14 09:52:51 -0700)
are available in the Git repository at:
https://github.com/cminyard/linux-ipmi.git tags/for-linus-6.11-1
for you to fetch changes up to 19a01155ddfe525e3a4e7cef734f18cce640b1ef:
ipmi: Drop explicit initialization of struct i2c_device_id::driver_data to 0 (2024-07-08 15:05:18 -0500)
----------------------------------------------------------------
IPMI: Small updates and fixes
Some cleanups for device changes coming, and some range checks on data
coming from a host to a BMC.
----------------------------------------------------------------
Dan Carpenter (1):
ipmi: ssif_bmc: prevent integer overflow on 32bit systems
Uwe Kleine-König (1):
ipmi: Drop explicit initialization of struct i2c_device_id::driver_data to 0
drivers/char/ipmi/ipmb_dev_int.c | 4 ++--
drivers/char/ipmi/ipmi_ipmb.c | 4 ++--
drivers/char/ipmi/ipmi_ssif.c | 2 +-
drivers/char/ipmi/ssif_bmc.c | 10 ++++++----
4 files changed, 11 insertions(+), 9 deletions(-)
next reply other threads:[~2024-07-16 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 13:28 Corey Minyard [this message]
2024-07-18 1:27 ` [GIT PULL] IPMI bug fixes for 6.11 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=ZpZ1dVeLWUbAd89V@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox