public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Catalin Marinas <catalin.marinas@arm•com>, Will Deacon <will@kernel•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Julien Thierry <julien.thierry@arm•com>
Subject: linux-next: Fixes tags need some work in the arm64 tree
Date: Fri, 21 Jun 2019 21:36:15 +1000	[thread overview]
Message-ID: <20190621213615.0efd4fa4@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 953 bytes --]

Hi all,

In commit

  86fc32fee888 ("arm64: Fix incorrect irqflag restore for priority masking")

Fixes tag

  Fixes: commit 4a503217ce37 ("arm64: irqflags: Use ICC_PMR_EL1 for interrupt masking")

has these problem(s):

  - leading word 'commit' unexpected

In commit

  1500e8ca63f4 ("arm64: Fix interrupt tracing in the presence of NMIs")

Fixes tag

  Fixes: bc3c03ccb ("arm64: Enable the support of pseudo-NMIs")

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").

In commit

  4a4063a9fbfa ("arm64: irqflags: Add condition flags to inline asm clobber list")

Fixes tag

  Fixes: commit 4a503217ce37 ("arm64: irqflags: Use ICC_PMR_EL1 for interrupt masking")

has these problem(s):

  - leading word 'commit' unexpected

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

next             reply	other threads:[~2019-06-21 11:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 11:36 Stephen Rothwell [this message]
2019-06-21 14:57 ` linux-next: Fixes tags need some work in the arm64 tree Catalin Marinas

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=20190621213615.0efd4fa4@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=julien.thierry@arm$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=will@kernel$(echo .)org \
    /path/to/YOUR_REPLY

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox