[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210407114650.2ed2p5aqkwwicm3k@gilmour>
Date: Wed, 7 Apr 2021 13:46:50 +0200
From: Maxime Ripard <maxime@...no.tech>
To: Arnd Bergmann <arnd@...db.de>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Olof Johansson <olof@...om.net>,
ARM <linux-arm-kernel@...ts.infradead.org>,
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 arm-soc tree
On Tue, Apr 06, 2021 at 11:44:27PM +0200, Arnd Bergmann wrote:
> On Tue, Apr 6, 2021 at 12:11 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > Hi all,
> >
> > On Tue, 6 Apr 2021 08:11:00 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > >
> > > Hi all,
> > >
> > > Commit
> > >
> > > 3b493ac0ac04 ("arm64: dts: allwinner: h6: Switch to macros for RSB clock/reset indices")
> > >
> > > is missing a Signed-off-by from its committer.
> >
> > Sorry, that commit is in the arm-soc-fixes tree.
>
> Thanks for the report, I've temporarily removed the sunx-fixes branch merge
> from the arm/fixes branch and will send the pull request without it.
>
> Maxime, can you fix it up and resend the pull request?
> Feel free to add any other fixes that have come up since then.
I just did. Is there a way to prevent this from happening when one
rebase a branch that was partially committed by someone else?
git rebase --signoff doesn't seem to detect if there's already a SoB, so
it might produce duplicates which isn't great either.
Maxime
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists