linux-kernel - Re: linux-next: Signed-off-by missing for commit in the gpio-brgl-fixes tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YEdCeICFjpbgD4UT@smile.fi.intel.com>
Date:   Tue, 9 Mar 2021 11:40:08 +0200
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Bartosz Golaszewski <brgl@...ev.pl>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the
 gpio-brgl-fixes tree

On Mon, Mar 08, 2021 at 11:01:44PM +0200, Andy Shevchenko wrote:
> On Mon, Mar 8, 2021 at 10:34 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > On Tue, 9 Mar 2021 07:26:20 +1100 Stephen Rothwell <sfr@...b.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.

I think I have to elaborate.
1/ you need to drop those commits from your tree (yeah, rebase :-(, nut you may
   do it interactively and inject the merge in the same location in the
   history)
2/ instead of cherry-picking them run something like
  git fetch git@...olite.kernel.org:pub/scm/linux/kernel/git/andy/linux-gpio-intel.git intel-gpio-v5.12-2
  git merge FETCH_HEAD

-- 
With Best Regards,
Andy Shevchenko