From: Hans de Goede <hdegoede@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Armin Wolf" <W_Armin@gmx.de>
Subject: [GIT PULL] platform-drivers-x86 for 6.10-6
Date: Wed, 10 Jul 2024 16:22:55 +0200 [thread overview]
Message-ID: <4f4c8c2a-c7ae-46bc-babb-7c6df4501df5@redhat.com> (raw)
Hi Linus,
Obviously I should not have jinxed things by saying that my previous pull-
request would be the last one for 6.10.
So here is one more 6.10 fixes pull-request with a 1 liner fix for
a dmi_system_id array in the toshiba_acpi driver not being terminated
properly. Something which somehow has escaped detection since being
introduced in 2022 until now.
Regards,
Hans
The following changes since commit e527a6127223b644e0a27b44f4b16e16eb6c7f0a:
platform/x86: toshiba_acpi: Fix quickstart quirk handling (2024-07-02 16:01:45 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git tags/platform-drivers-x86-v6.10-6
for you to fetch changes up to b6e02c6b0377d4339986e07aeb696c632cd392aa:
platform/x86: toshiba_acpi: Fix array out-of-bounds access (2024-07-10 16:12:12 +0200)
----------------------------------------------------------------
platform-drivers-x86 for v6.10-6
Highlights:
- Fix missing dmi_system_id array termination in toshiba_acpi introduced in 2022
The following is an automated git shortlog grouped by driver:
toshiba_acpi:
- Fix array out-of-bounds access
----------------------------------------------------------------
Armin Wolf (1):
platform/x86: toshiba_acpi: Fix array out-of-bounds access
drivers/platform/x86/toshiba_acpi.c | 1 +
1 file changed, 1 insertion(+)
next reply other threads:[~2024-07-10 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 14:22 Hans de Goede [this message]
2024-07-10 16:14 ` 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=4f4c8c2a-c7ae-46bc-babb-7c6df4501df5@redhat.com \
--to=hdegoede@redhat.com \
--cc=W_Armin@gmx.de \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--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
all inboxes | Powered by JetHome®