From: Hans de Goede <hdegoede@redhat.com>
To: Wentong Wu <wentong.wu@intel.com>,
Alexander Usyskin <alexander.usyskin@intel.com>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] mei: vsc: Fix kernel-crash when build with gcc 15
Date: Tue, 18 Mar 2025 15:12:01 +0100 [thread overview]
Message-ID: <20250318141203.94342-1-hdegoede@redhat.com> (raw)
Hi All,
Here are 2 fixes for the vsc-tp mei code. The first patch fixes
a kernel crash when the kernel is build with gcc 15 and it would be
get to get this upstream ASAP.
The second patch is just a small cleanup of something which I noticed
when working on the fix.
Regards,
Hans
Hans de Goede (2):
mei: vsc: Fix fortify-panic caused by invalid counted_by() use
mei: vsc: Use struct vsc_tp_packet as vsc-tp tx_buf and rx_buf type
drivers/misc/mei/vsc-tp.c | 40 +++++++++++++++++++++------------------
1 file changed, 22 insertions(+), 18 deletions(-)
--
2.48.1
next reply other threads:[~2025-03-18 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 14:12 Hans de Goede [this message]
2025-03-18 14:12 ` [PATCH 1/2] mei: vsc: Fix fortify-panic caused by invalid counted_by() use Hans de Goede
2025-03-20 14:12 ` Usyskin, Alexander
2025-05-04 8:25 ` Mateusz Schyboll
2025-05-04 8:56 ` Hans de Goede
2025-05-04 9:13 ` Mateusz Schyboll
2025-03-18 14:12 ` [PATCH 2/2] mei: vsc: Use struct vsc_tp_packet as vsc-tp tx_buf and rx_buf type Hans de Goede
2025-03-20 14:13 ` Usyskin, Alexander
2025-03-18 14:44 ` [PATCH 0/2] mei: vsc: Fix kernel-crash when build with gcc 15 Sakari Ailus
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=20250318141203.94342-1-hdegoede@redhat.com \
--to=hdegoede@redhat.com \
--cc=alexander.usyskin@intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=stanislaw.gruszka@linux.intel.com \
--cc=wentong.wu@intel.com \
/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®