From: Andy Shevchenko <andy.shevchenko@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Andy Shevchenko <andriy.shevchenko@linux•intel.com>,
Bartosz Golaszewski <brgl@bgdev•pl>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the gpio-brgl-fixes tree
Date: Mon, 8 Mar 2021 23:01:44 +0200 [thread overview]
Message-ID: <CAHp75Ve2qGd5fFC9ztaEk9d+YBa-aTu-gMn_9dRUbpkWGY9YTw@mail.gmail.com> (raw)
In-Reply-To: <20210309073211.392a838d@canb.auug.org.au>
On Mon, Mar 8, 2021 at 10:34 PM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Hi all,
>
> On Tue, 9 Mar 2021 07:26:20 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > Commits
> >
> > eb441337c714 ("gpio: pca953x: Set IRQ type when handle Intel Galileo Gen 2")
> > 809390219fb9 ("gpiolib: acpi: Allow to find GpioInt() resource by name and index")
> > 62d5247d239d ("gpiolib: acpi: Add ACPI_GPIO_QUIRK_ABSOLUTE_NUMBER quirk")
> > 6e5d5791730b ("gpiolib: acpi: Add missing IRQF_ONESHOT")
> >
> > are missing a Signed-off-by from their committers.
>
> This also applies to the gpio-intel-fixes tree (since it is now headed
> by the same commit as the gpio-brgl-fixes tree).
I rebased my branch according to Linus, but I have decided to take
directly Bart's tree.
So when original will be fixed I'll fix mine.
Thanks!
P.S. Bart, you may simply merge my tag even on top of v5.12-rc2. It
will save you time and keep the original SHA IDs.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-03-08 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 20:26 linux-next: Signed-off-by missing for commit in the gpio-brgl-fixes tree Stephen Rothwell
2021-03-08 20:32 ` Stephen Rothwell
2021-03-08 21:01 ` Andy Shevchenko [this message]
2021-03-09 9:40 ` Andy Shevchenko
2021-03-10 12: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=CAHp75Ve2qGd5fFC9ztaEk9d+YBa-aTu-gMn_9dRUbpkWGY9YTw@mail.gmail.com \
--to=andy.shevchenko@gmail$(echo .)com \
--cc=andriy.shevchenko@linux$(echo .)intel.com \
--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 \
/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