From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: soc <soc@lists.linux.dev>
Cc: linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Joel Stanley <joel@jms.id.au>
Subject: [GIT PULL] aspeed: First batch of driver fixes for 7.2
Date: Tue, 04 Aug 2026 16:14:50 +0930 [thread overview]
Message-ID: <3da63bea367b3490b041c909a4503cc2b5e9c394.camel@codeconstruct.com.au> (raw)
Hello SoC maintainers,
The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:
Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/bmc/linux.git tags/aspeed-7.2-driver-fixes-0
for you to fetch changes up to 1acef6d85bfd98bd9dfe1f08bffa397a4dda8a6f:
soc: aspeed: lpc-snoop: Fix usercopy overflow in snoop_file_read (2026-07-22 22:10:54 +0930)
----------------------------------------------------------------
aspeed: First batch of driver fixes for 7.2
This time it's a single fix for a kfifo overrun, caused by the the lpc-snoop
driver implementation behaving as multiple consumers.
----------------------------------------------------------------
Karthikeyan KS (1):
soc: aspeed: lpc-snoop: Fix usercopy overflow in snoop_file_read
drivers/soc/aspeed/Makefile | 1 +
drivers/soc/aspeed/aspeed-lpc-snoop.c | 38 ++++++++++++++++++++++++-----------
2 files changed, 27 insertions(+), 12 deletions(-)
next reply other threads:[~2026-08-04 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 6:44 Andrew Jeffery [this message]
2026-08-04 20:20 ` [GIT PULL] aspeed: First batch of driver fixes for 7.2 patchwork-bot+linux-soc
2026-08-04 20:20 ` patchwork-bot+linux-soc
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=3da63bea367b3490b041c909a4503cc2b5e9c394.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@lists.linux.dev \
/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