public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux•intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	Bartosz Golaszewski <brgl@bgdev•pl>,
	Werner Sembach <wse@tuxedocomputers•com>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: duplicate patch in the gpio-intel tree
Date: Mon, 27 Mar 2023 13:36:51 +0300	[thread overview]
Message-ID: <ZCFxw+6QGYJzl+sK@smile.fi.intel.com> (raw)
In-Reply-To: <CACMJSevvO0B8O0K4HtdTdxsGYGVfyHOug=qSg00SwVU+vw8Xsw@mail.gmail.com>

On Mon, Mar 27, 2023 at 09:14:00AM +0200, Bartosz Golaszewski wrote:
> On Mon, 27 Mar 2023 at 02:20, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > Hi all,
> >
> > The following commits are also in the gpio-brgl-fixes tree as a different
> > commit (but the same patch):
> >
> >   782eea0c89f7 ("gpiolib: acpi: Add a ignore wakeup quirk for Clevo NL5xNU")
> >
> > This is commit
> >
> >   a21031ccf31b ("gpiolib: acpi: Add a ignore wakeup quirk for Clevo NL5xNU")
> >
> > in the gpio-brgl-fixes tree.
> >
> I missed the fact Andy already picked it up. Now backed out of my tree.

Oh, thank you, folks. for sorting this out!


-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2023-03-27 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27  0:20 linux-next: duplicate patch in the gpio-intel tree Stephen Rothwell
2023-03-27  7:14 ` Bartosz Golaszewski
2023-03-27 10:36   ` 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=ZCFxw+6QGYJzl+sK@smile.fi.intel.com \
    --to=andriy.shevchenko@linux$(echo .)intel.com \
    --cc=bartosz.golaszewski@linaro$(echo .)org \
    --cc=brgl@bgdev$(echo .)pl \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=wse@tuxedocomputers$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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