[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200728081959.2df754d0@canb.auug.org.au>
Date: Tue, 28 Jul 2020 08:19:59 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: John Ogness <john.ogness@...utronix.de>
Cc: 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
Hi John,
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:
> > 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
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists