[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdY1UtTtRK7LaUxrBFRFooeT4s7h0GSKHNhsZrrMtJ5=3A@mail.gmail.com>
Date: Fri, 17 Apr 2020 12:32:11 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Serge Semin <Sergey.Semin@...kalelectronics.ru>,
Andy Shevchenko <andy.shevchenko@...il.com>
Subject: Re: linux-next: Signed-off-by missing for commits in the gpio tree
On Fri, Apr 17, 2020 at 12:28 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Commits
>
> fe5dfc6af3eb ("MAINTAINERS: Add Segey Semin to maintainers of DW APB GPIO driver")
> 49a369f94046 ("gpio: dwapb: Add debounce reference clock support")
> cbabbfa160bd ("gpio: dwapb: Use optional-clocks interface for APB ref-clock")
> fb7e1fc1b806 ("dt-bindings: gpio: Add Sergey Semin to DW APB GPIO driver maintainers")
> 7f51dbb7cab7 ("dt-bindings: gpio: Add DW GPIO debounce clock property")
> 179587eb757f ("dt-bindings: gpio: Convert snps,dw-apb-gpio to DT schema")
>
> are missing a Signed-off-by from their committer.
Ooops I hurt myself on the b4 tool, forgetting to pass --signoff to the
resulting git am foo.mbx... need to learn habits.
Sometimes I feel there should be some git am hook that just enforce
my --signoff on branches that go upstream so it can't go wrong.
Has anyone seen something like that?
Yours,
Linus Walleij
Powered by blists - more mailing lists