Re: linux-next: Fixes tag needs some work in the printk tree

[Sergey Senozhatsky]

On (20/07/28 08:19), Stephen Rothwell wrote:
> On Mon, 27 Jul 2020 17:13:44 +0206 John Ogness <john.ogness@xxxxxxxxxxxxx> wrote:
> >
> > On 2020-07-27, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> 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