All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Xu <peterx@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the mm-hotfixes tree
Date: Mon, 8 Aug 2022 07:19:41 +1000	[thread overview]
Message-ID: <20220808071941.4e18e748@canb.auug.org.au> (raw)

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

Hi all,

In commit

  b2f4c6e29531 ("mm/smaps: don't access young/dirty bit if pte unpresent")

Fixes tag

  Fixes: b1d4d9e0cbd0 ("proc/smaps: carefully handle migration entries", 2012-05-31)

has these problem(s):

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

Please do not include the date part - it adds nothing.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2022-08-07 22:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-07 21:19 Stephen Rothwell [this message]
2022-08-07 23:01 ` linux-next: Fixes tag needs some work in the mm-hotfixes tree Peter Xu
  -- strict thread matches above, loose matches on Subject: below --
2025-12-09  4:08 Stephen Rothwell
2025-09-10  7:32 Stephen Rothwell
2025-08-26  9:08 Stephen Rothwell
2025-08-20  4:50 Stephen Rothwell
2025-08-12  6:44 Stephen Rothwell
2025-08-12 13:46 ` Pasha Tatashin
2025-08-12 20:12   ` Andrew Morton
2024-10-07 20:44 Stephen Rothwell
2024-08-25 21:26 Stephen Rothwell
2024-08-04 21:17 Stephen Rothwell
2024-08-05  2:47 ` Muchun Song
2024-07-02 22:09 Stephen Rothwell
2023-11-29 20:43 Stephen Rothwell
2023-11-30  1:07 ` Baoquan He
2023-06-07  4:35 Stephen Rothwell
2022-04-27 22:36 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=20220808071941.4e18e748@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=peterx@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.