From: Zach O'Keefe <zokeefe@google.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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 mm tree
Date: Mon, 19 Sep 2022 07:47:51 -0700 [thread overview]
Message-ID: <YyiBF5V6I7SYHqJy@google.com> (raw)
In-Reply-To: <20220919082105.73c0e270@canb.auug.org.au>
On Sep 19 08:21, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 3a41f36f7083 ("selftests/vm: fix "add thp collapse file and tmpfs testing" for tmpfs")
>
> Fixes tag
>
> Fixes: 64b9fb1fa904 ("selftests/vm: add thp collapse file and tmpfs testing")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
>
> So
>
> Fixes: 64b9fb1fa904 ("selftests/vm: add thp collapse shmem testing")
>
> or maybe
>
> Fixes: 465c955b7343 ("selftests/vm: add thp collapse file and tmpfs testing")
>
> --
> Cheers,
> Stephen Rothwell
Hey Stephen,
Apologies here. Yes, the correct Fixes tag should be, based off latest
mm-unstable,
Fixes: 8d88fef0b3d8 ("selftests/vm: add thp collapse file and tmpfs testing")
Now, I'm quite confused as to has this happened as I've been generating
citations using something similar to the --format string you reference, but
perhaps this time I chose to do it manually and messed it up. Anyways, will
write something to catch these mistakes in the future.
Andrew, there are a few changes incoming to the "mm: add file/shmem support to
MADV_COLLAPSE" series based off recent reviews (including another patch with
a commit description change). Perhaps it's easier for me to send a new (v4)
series to mm-unstable to address these? Otherwise, I'm not sure how to
request these metadata changes.
Best,
Zach
next prev parent reply other threads:[~2022-09-19 14:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 22:21 linux-next: Fixes tag needs some work in the mm tree Stephen Rothwell
2022-09-19 14:47 ` Zach O'Keefe [this message]
2022-09-19 21:04 ` Andrew Morton
2022-09-21 18:24 ` Zach O'Keefe
-- strict thread matches above, loose matches on Subject: below --
2025-02-09 6:22 Stephen Rothwell
2024-07-09 22:54 Stephen Rothwell
2024-02-25 21:18 Stephen Rothwell
2024-02-04 21:29 Stephen Rothwell
2023-12-12 20:59 Stephen Rothwell
2023-12-13 1:04 ` Andrew Morton
2023-10-17 4:33 Stephen Rothwell
2023-10-10 5:47 Stephen Rothwell
2023-10-10 15:42 ` Zi Yan
2022-11-23 22:08 Stephen Rothwell
2022-11-23 23:06 ` Jann Horn
2022-11-24 0:13 ` Andrew Morton
2022-11-24 13:37 ` Jann Horn
2022-11-23 22:00 Stephen Rothwell
2022-07-26 23:23 Stephen Rothwell
2022-07-27 0:02 ` Andrew Morton
2022-06-30 3:37 Stephen Rothwell
2022-06-30 15:28 ` Liam Howlett
2022-06-30 18:16 ` Andrew Morton
2022-06-30 3:32 Stephen Rothwell
2022-06-30 15:20 ` Liam Howlett
2022-05-25 0:27 Stephen Rothwell
2022-05-25 0:36 ` Zi Yan
2022-05-13 6:56 Stephen Rothwell
2022-04-27 22:42 Stephen Rothwell
2022-04-28 2:37 ` Liam Howlett
2022-04-28 3:09 ` Andrew Morton
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=YyiBF5V6I7SYHqJy@google.com \
--to=zokeefe@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.