LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Cc: Roberto Sassu <roberto.sassu@huawei.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 integrity tree
Date: Tue, 01 Jun 2021 18:54:28 -0400	[thread overview]
Message-ID: <1bb738125345283693fb41ea188e934b3d33ae75.camel@linux.ibm.com> (raw)
In-Reply-To: <20210602080742.1832f12c@canb.auug.org.au>

On Wed, 2021-06-02 at 08:07 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   9eea2904292c ("evm: Execute evm_inode_init_security() only when an HMAC key is loaded")
> 
> Fixes tag
> 
>   Fixes: 26ddabfe96b ("evm: enable EVM when X509 certificate is loaded")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
> 
> Probably not worth rebasing for, but can be avoided in 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").

Stephen, thank you for catching the short hash.  It would be nice if
checkpatch would be updated to catch it.  I recently noticed
Documentation/process/submitting-patches.rst has directions for setting
up "--pretty=fixes".

thanks,

Mimi


  reply	other threads:[~2021-06-01 22:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 22:07 Stephen Rothwell
2021-06-01 22:54 ` Mimi Zohar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-23 22:18 Stephen Rothwell
2021-08-24  7:11 ` THOBY Simon
2021-08-24 12:19   ` Mimi Zohar
2021-05-20 22:12 Stephen Rothwell

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=1bb738125345283693fb41ea188e934b3d33ae75.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=roberto.sassu@huawei.com \
    --cc=sfr@canb.auug.org.au \
    --cc=zohar@linux.vnet.ibm.com \
    --subject='Re: linux-next: Fixes tag needs some work in the integrity tree' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).