linux-kernel - Re: linux-next: Fixes tag needs some work in the input-current 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]

Date:   Fri, 25 Jan 2019 15:58:36 -0800
From:   Dmitry Torokhov <dmitry.torokhov@...il.com>
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>,
        Lubomir Rintel <lkundrak@...sk>
Subject: Re: linux-next: Fixes tag needs some work in the input-current tree

On Fri, Jan 25, 2019 at 3:56 PM Dmitry Torokhov
<dmitry.torokhov@...il.com> wrote:
>
> Hi Stephen,
>
> On Thu, Jan 24, 2019 at 3:09 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > Hi Dmitry,
> >
> > In commit
> >
> >   ec87da107d11 ("Input: olpc_apsp - assign priv->dev earlier")
> >
> > Fixes tag
> >
> >   Fixes: commit af518342effd ("Input: olpc_apsp - check FIFO status on open(), not probe()")
> >
> > has these problem(s):
> >
> >   - No SHA1 recognised
> >
> > The "commit" at the start of the tag value was unexpected.
>
> Hmm, this is really weird:
>
> dtor@...r-ws:~/kernel/master (for-linus)$ git log --oneline --
> drivers/input/serio/olpc_apsp.c
> ec87da107d11 Input: olpc_apsp - assign priv->dev earlier
> 2a58dd767bf9 Input: olpc_apsp - remove set but not used variable 'np'
> ed22cee91a88 Input: olpc_apsp - enable the SP clock
> af518342effd Input: olpc_apsp - check FIFO status on open(), not probe()
>
> As you can see there is that SHA1 in question present in my for-linus branch.

Argh, I see what you mean, the word "commit" should be omitted. Oh
well, it's in the branch that I loath to rebase, so it will have to
stay as is.

-- 
Dmitry