public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Aaron Tomlin <atomlin@redhat•com>,
	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 modules tree
Date: Tue, 5 Apr 2022 08:45:54 -0700	[thread overview]
Message-ID: <YkxkMiSt1SnCLrGc@bombadil.infradead.org> (raw)
In-Reply-To: <20220405081529.28925a1f@canb.auug.org.au>

On Tue, Apr 05, 2022 at 08:15:29AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   450f0134ccf0 ("module: Make internal.h and decompress.c more compliant")
> 
> Fixes tag
> 
>   Fixes: f314dfea16a ("modsign: log module name in the event of an error")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     This can be fixed for the future 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").

Fixed, thanks!

  Luis

  reply	other threads:[~2022-04-05 21:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 22:15 linux-next: Fixes tag needs some work in the modules tree Stephen Rothwell
2022-04-05 15:45 ` Luis Chamberlain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-23 22:33 Stephen Rothwell
2023-07-24 19:11 ` Luis Chamberlain
2022-03-01  0:33 Stephen Rothwell
2022-03-01  0:43 ` Luis Chamberlain
2021-01-18 19:35 Stephen Rothwell
2020-02-17 20:38 Stephen Rothwell
2020-02-17 20:42 ` Jessica Yu
2019-04-30 22:10 Stephen Rothwell
2019-04-30 22:13 ` Prarit Bhargava
2019-05-01  8:03 ` Jessica Yu

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=YkxkMiSt1SnCLrGc@bombadil.infradead.org \
    --to=mcgrof@kernel$(echo .)org \
    --cc=atomlin@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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