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: Thu, 19 Nov 2020 12:59:23 +0200 [thread overview]
Message-ID: <20201119105923.GA4077@smile.fi.intel.com> (raw)
In-Reply-To: <20201119105828.GZ4077@smile.fi.intel.com>
On Thu, Nov 19, 2020 at 12:58:28PM +0200, Andy Shevchenko wrote:
> On Thu, Nov 19, 2020 at 09:31:03AM +0100, Linus Walleij wrote:
> > On Wed, Nov 18, 2020 at 3:17 PM Andy Shevchenko
> > <andriy.shevchenko@linux.intel.com> wrote:
> > > On Tue, Nov 17, 2020 at 10:24:37PM +0100, Linus Walleij wrote:
> >
> > > > 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!
> >
> > I merged v5.10-rc4 because the pull request says:
> >
> > > The following changes since commit b72de3ff19fdc4bbe4d4bb3f4483c7e46e00bac3:
> > >
> > > gpio: sifive: Fix SiFive gpio probe (2020-11-11 09:53:09 +0100)
> >
> > And that patch was on my fixes branch, which went into v5.10-rc4,
> > so in order to have the base commit in the devel tree I had to merge
> > in v5.10-rc4.
>
> I based solely on your gpio/for-next as has been stated in the cover letter.
> So, the PR might have been applied on top of your gpio/for-next without any
> additional merge required.
>
> I admit that PR automatic text is a bit deviated (it has been taken from wrong
> base, note that tag is correct nevertheless). I will look forward to amend my
"information in the tag"
> scripts.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-11-19 10:58 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
2020-11-19 8:31 ` Linus Walleij
2020-11-19 10:58 ` Andy Shevchenko
2020-11-19 10:59 ` Andy Shevchenko [this message]
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=20201119105923.GA4077@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.