All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Linux GPIO <linux-gpio@vger.kernel.org>,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [GIT PULL] intel-gpio for 5.11-1
Date: Wed, 18 Nov 2020 16:18:11 +0200	[thread overview]
Message-ID: <20201118141811.GV4077@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdbgO++4scNqX=3D0XKSyUhah67UvMjHDbaT4SyX0ESF-A@mail.gmail.com>

On Tue, Nov 17, 2020 at 10:24:37PM +0100, Linus Walleij wrote:
> On Mon, Nov 16, 2020 at 4:26 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> 
> > The following changes since commit b72de3ff19fdc4bbe4d4bb3f4483c7e46e00bac3:
> >
> >   gpio: sifive: Fix SiFive gpio probe (2020-11-11 09:53:09 +0100)
> >
> > are available in the Git repository at:
> >
> >   git@gitolite.kernel.org:pub/scm/linux/kernel/git/andy/linux-gpio-intel.git tags/intel-gpio-v5.11-1
> >
> > for you to fetch changes up to e709a7b5a066362b697d65dda90edc71f913df70:
> >
> >   gpiolib: acpi: Make Intel GPIO tree official for GPIO ACPI work (2020-11-16 14:14:35 +0200)
> 
> Thanks! I merged in v5.10-rc4 to the GPIO devel branch and
> pulled in this on top, works like a charm!

I'm not sure I understood why you merged v5.10-rc4, but in any case thanks,
result is great!

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2020-11-18 14:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 15:26 [GIT PULL] intel-gpio for 5.11-1 Andy Shevchenko
2020-11-17 21:24 ` Linus Walleij
2020-11-18 14:18   ` Andy Shevchenko [this message]
2020-11-19  8:31     ` Linus Walleij
2020-11-19 10:58       ` Andy Shevchenko
2020-11-19 10:59         ` Andy Shevchenko
2020-11-19 12:43         ` Linus Walleij
2020-11-19 13:29           ` 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=20201118141811.GV4077@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=hdegoede@redhat.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    /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.