From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linux GPIO <linux-gpio@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [GIT PULL] intel-gpio for 5.17-1
Date: Thu, 16 Dec 2021 15:05:18 +0200 [thread overview]
Message-ID: <Ybs5jqW3zyDh18Vx@smile.fi.intel.com> (raw)
In-Reply-To: <CAMRc=McSULw2YpCgsK-C6+pTx85mtH3c5Y+MbawO+SSgUXM1gg@mail.gmail.com>
On Thu, Dec 16, 2021 at 12:46:11PM +0100, Bartosz Golaszewski wrote:
> On Thu, Dec 16, 2021 at 12:37 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > On Thu, Dec 16, 2021 at 10:14:05AM +0100, Bartosz Golaszewski wrote:
> > > On Wed, Dec 15, 2021 at 3:33 PM Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> wrote:
> > > >
> > > > Hi Linux GPIO maintainers,
> > > >
> > > > Approximately a dozen of changes for v5.17 against Intel GPIO drivers and
> > > > GPIO ACPI library. It has ben a while in Linux Next without any error reported.
> >
> > > Pulled, thanks!
> >
> > Thanks!
> >
> > Are you going to pull series with the OF node assignments clean up?
> > I forgot to mention here that my PR does not include them.
> >
>
> Yes, I'll queue it this week.
Thanks!
Do you know that your branches were kicked off from the Linux Next?
Are you going to drop previous gpio-sim from the Linux Next?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-12-16 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 14:33 [GIT PULL] intel-gpio for 5.17-1 Andy Shevchenko
2021-12-16 9:14 ` Bartosz Golaszewski
2021-12-16 11:36 ` Andy Shevchenko
2021-12-16 11:46 ` Bartosz Golaszewski
2021-12-16 13:05 ` Andy Shevchenko [this message]
2021-12-16 13:13 ` Andy Shevchenko
2021-12-16 14:01 ` Bartosz Golaszewski
2021-12-17 9:52 ` Andy Shevchenko
2021-12-17 11:13 ` Bartosz Golaszewski
2021-12-17 11:29 ` Bartosz Golaszewski
2021-12-17 11:47 ` Andy Shevchenko
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=Ybs5jqW3zyDh18Vx@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.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