From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Linus Walleij <linusw@kernel.org>,
Andy Shevchenko <andy@kernel.org>,
Linux GPIO <linux-gpio@vger.kernel.org>
Subject: Re: [GIT PULL] intel-gpio for 7.3-1
Date: Thu, 15 Oct 2026 16:19:11 +0300 [thread overview]
Message-ID: <atDSz_8Xw8bGuWfd@ashevche-desk.local> (raw)
In-Reply-To: <CAMRc=Mf9s7XkM=8cv0WZ_wB=nv92cKyD1q3Kr70HaJ7kHjmYxw@mail.gmail.com>
On Thu, Oct 15, 2026 at 01:06:13PM +0000, Bartosz Golaszewski wrote:
> On Thu, 15 Oct 2026 14:52:58 +0200, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> said:
> > Hi Linux GPIO maintainers,
> >
> > A small set of fixes for GPIO on ACPI-based platforms. It was in Linux Next
> > for a while without regressions reported. Please, pull and send as a fix set
> > for current, v7.3, release.
> >
> > Thanks,
> >
> > With Best Regards,
> > Andy Shevchenko
> >
> > The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:
> >
> > Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
> >
> > are available in the Git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/andy/linux-gpio-intel.git tags/intel-gpio-v7.3-1
> >
> > for you to fetch changes up to 3fd4bf93d586cb07304cdcb5e8b3c51ac1d8284f:
> >
> > gpiolib: acpi: Fix GPIO lookup using relative path (2026-10-13 22:34:07 +0200)
> >
>
> Thanks, pulled. There was a trivial conflict fixed like so:
Oh, yes, forgot to mentioned that. Resolution is straight forward and you got
it right, thanks!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-10-15 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 12:52 [GIT PULL] intel-gpio for 7.3-1 Andy Shevchenko
2026-10-15 13:06 ` Bartosz Golaszewski
2026-10-15 13:19 ` Andy Shevchenko [this message]
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=atDSz_8Xw8bGuWfd@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy@kernel.org \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.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