From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Mika Westerberg <westeri@kernel.org>,
Linus Walleij <linusw@kernel.org>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Marco Scardovi <scardracs@disroot.org>
Subject: Re: [PATCH v6 0/2] gpiolib: acpi: Add robust bounds-checking and safe address handling
Date: Tue, 16 Jun 2026 13:26:06 +0300 [thread overview]
Message-ID: <ajEkvstS6RgRTATK@ashevche-desk.local> (raw)
In-Reply-To: <CAMRc=Mcv7SWVYA6rNZo+-tYx_ohOdedkewLZOa=X1Eei=1fTzA@mail.gmail.com>
On Tue, Jun 16, 2026 at 02:54:02AM -0700, Bartosz Golaszewski wrote:
> On Fri, 12 Jun 2026 10:52:57 +0200, Mika Westerberg
> <mika.westerberg@linux.intel.com> said:
> > On Wed, Jun 10, 2026 at 05:42:02PM +0200, Marco Scardovi wrote:
> >>
> >> The series adds explicit bounds checking for GPIO pin accesses and
> >> ensures safe handling of ACPI addresses in OperationRegion handlers,
> >> without referring to truncation or wrap-around behavior, which does
> >> not apply.
> >
> > I'm fine with these now.
> >
> > For both,
> >
> > Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>
> Andy, Mika: do you want me to queue these directly for v7.2?
I believe there is no hurry, but I have no objections if you pull it in.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-06-16 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 15:42 Marco Scardovi
2026-06-10 15:42 ` [PATCH v6 1/2] gpiolib: acpi: Add robust bounds-checking for GPIO pin resources Marco Scardovi
2026-06-10 15:42 ` [PATCH v6 2/2] gpiolib: acpi: Prevent out-of-bounds pin access in OperationRegion handler Marco Scardovi
2026-06-12 8:52 ` [PATCH v6 0/2] gpiolib: acpi: Add robust bounds-checking and safe address handling Mika Westerberg
2026-06-16 9:54 ` Bartosz Golaszewski
2026-06-16 10:26 ` Andy Shevchenko [this message]
2026-06-16 10:42 ` Bartosz Golaszewski
2026-06-16 11:28 ` Andy Shevchenko
2026-06-16 11:48 ` Mika Westerberg
2026-06-17 6:14 ` Bartosz Golaszewski
2026-06-17 6:14 ` Bartosz Golaszewski
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=ajEkvstS6RgRTATK@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=scardracs@disroot.org \
--cc=westeri@kernel.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®