linux-kernel - Re: linux-next: Fixes tag needs some work in the printk 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] [day] [month] [year] [list]

Message-ID: <20200728012257.GA1282472@jagdpanzerIV.localdomain>
Date:   Tue, 28 Jul 2020 10:22:57 +0900
From:   Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     John Ogness <john.ogness@...utronix.de>,
        Petr Mladek <pmladek@...e.com>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Subject: Re: linux-next: Fixes tag needs some work in the printk tree

On (20/07/28 08:19), Stephen Rothwell wrote:
> On Mon, 27 Jul 2020 17:13:44 +0206 John Ogness <john.ogness@...utronix.de> wrote:
> >
> > On 2020-07-27, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
[..]
> > > Maybe you meant
> > >
> > > Fixes: 896fbe20b4e2 ("printk: use the lockless ringbuffer")  
> >
> > Yes, sorry. I did not think linux-next SHA1 hashes were used in commit
> > logs.

Neither did I. The tag made sense to me, because it fixes a regression
after all.

> Well, it makes sense to use them if they are stable (i.e. the tree they
> are in does not rebase) which, by this part of the cycle, I would
> *hope* would be true (but sometimes isn't :-().

So we probably should not have Fixes tags in linux-next commits
(printk rework branch) then, for the time being. I'll keep an eye
on that.

	-ss