Hi John,
On Mon, 27 Jul 2020 17:13:44 +0206 John Ogness <john.ogness@xxxxxxxxxxxxx> wrote:
>
> On 2020-07-27, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
> > In commit
> >
> > 96b917f8e9ec ("printk: ringbuffer: support dataless records")
> >
> > Fixes tag
> >
> > Fixes: ("printk: use the lockless ringbuffer")
> >
> > has these problem(s):
> >
> > - No SHA1 recognised
> >
> > 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.
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 :-().
--
Cheers,
Stephen Rothwell
Attachment:
pgpfTLZ0s7TTf.pgp
Description: OpenPGP digital signature
