linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jan Beulich <jbeulich@suse.com>,
	Fabien Parent <fparent@baylibre.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: linux-next: Fixes tags need some work in the tip tree
Date: Tue, 5 Nov 2019 22:18:30 +1100	[thread overview]
Message-ID: <20191105221830.69ec8bcc@canb.auug.org.au> (raw)

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

Hi all,

In commit

  fe6f85ca121e ("x86/apic/32: Avoid bogus LDR warnings")

Fixes tag

  Fixes: bae3a8d3308 ("x86/apic: Do not initialize LDR and DFR for bigsmp")

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

  41d49e7939de ("clocksource/drivers/mediatek: Fix error handling")

Fixes tag

  Fixes: a0858f937960 ("mediatek: Convert the driver to timer-of")

has these problem(s):

  - Subject does not match target commit subject
    Just use
	git log -1 --format='Fixes: %h ("%s")'

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2019-11-05 11:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 11:18 Stephen Rothwell [this message]
2019-11-05 11:52 ` linux-next: Fixes tags need some work in the tip tree Thomas Gleixner
  -- strict thread matches above, loose matches on Subject: below --
2021-03-08  2:16 Stephen Rothwell
2021-03-08  8:38 ` Ingo Molnar
2020-01-15 20:03 Stephen Rothwell
2019-10-22 20:16 Stephen Rothwell
2019-10-22 20:30 ` Thomas Hellstrom
2019-10-23 10:16   ` Ingo Molnar

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=20191105221830.69ec8bcc@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=daniel.lezcano@linaro.org \
    --cc=fparent@baylibre.com \
    --cc=hpa@zytor.com \
    --cc=jbeulich@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).