All of lore.kernel.org
 help / color / mirror / Atom feed
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:13:46 +0200	[thread overview]
Message-ID: <Ybs7io7zg4+rsfWf@smile.fi.intel.com> (raw)
In-Reply-To: <Ybs5jqW3zyDh18Vx@smile.fi.intel.com>

On Thu, Dec 16, 2021 at 03:05:18PM +0200, Andy Shevchenko wrote:
> 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?


Last seen GPIO for-next
$ git tag --contains 9dbd1ab2050
next-20211207
next-20211208
next-20211210

Last seen your old GPIO simulator
$ git tag --contains 5065e08e4ef3c
DONT-USE-next-20211105
next-20211101
next-20211102
next-20211103
next-20211104
next-20211105
next-20211106
next-20211108
next-20211109
next-20211110
next-20211111
next-20211112
next-20211115
next-20211116
next-20211117
next-20211118
next-20211123
next-20211124
next-20211125
next-20211126
next-20211129
next-20211130
next-20211201
next-20211202
next-20211203
next-20211206
next-20211207
next-20211208
next-20211210
next-20211213
next-20211214
next-20211215


-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2021-12-16 13:14 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
2021-12-16 13:13         ` Andy Shevchenko [this message]
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=Ybs7io7zg4+rsfWf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.