public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the printk tree
Date: Tue, 3 Nov 2020 09:46:06 +0100	[thread overview]
Message-ID: <20201103084606.GK20201@alley> (raw)
In-Reply-To: <20201103083201.4c653eed@canb.auug.org.au>

On Tue 2020-11-03 08:32:01, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   8a8424bf2439 ("init/Kconfig: Fix CPU number in LOG_CPU_MAX_BUF_SHIFT description")
> 
> Fixes tag
> 
>   Fixes: 23b2899f7f ("printk: allow increasing the ring buffer depending on the number of CPUs")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
>     or later) just making sure it is not set (or set to "auto").

Should be fixed now. It is a pity that checkpatch.pl did not warn
about it.

Thanks for the report.

Best Regards,
Petr

  reply	other threads:[~2020-11-03  8:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 21:32 linux-next: Fixes tag needs some work in the printk tree Stephen Rothwell
2020-11-03  8:46 ` Petr Mladek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-23 21:53 Stephen Rothwell
2025-11-24 14:54 ` Petr Mladek
2021-07-11  3:01 Stephen Rothwell
2020-07-27 13:46 Stephen Rothwell
2020-07-27 15:07 ` John Ogness
2020-07-27 22:19   ` Stephen Rothwell
2020-07-28  1:22     ` Sergey Senozhatsky
2019-04-25 13:30 Stephen Rothwell
2019-04-26  7:37 ` Petr Mladek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201103084606.GK20201@alley \
    --to=pmladek@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox