From: Mike Kravetz <mike.kravetz@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation•org>,
Linus Torvalds <torvalds@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-stable tree
Date: Sun, 9 Oct 2022 18:40:15 -0700 [thread overview]
Message-ID: <Y0N3/wtn3dR2h6TT@monkey> (raw)
In-Reply-To: <20221009193544.27055db5@canb.auug.org.au>
On 10/09/22 19:35, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> bbff39cc6cbc ("hugetlb: allocate vma lock for all sharable vmas")
>
> Fixes tag
>
> Fixes: "hugetlb: clean up code checking for fault/truncation races"
>
> has these problem(s):
>
> - No SHA1 recognised
>
> Maybe you meant
>
> Fixes: fa27759af4a6 ("hugetlb: clean up code checking for fault/truncation races")
For all of these, I was under the impression that the SHA1 of commits in
Andrew's trees were not stable and could change. That is why I purposely
did not try to add SHA1s to the tags. Perhaps that is no longer the case
since Andrew is using git to manage patches?
I see that a pull request including these commits was already sent to
Linus. Not sure where these are in the process, or if it may be too
late to update. Let me know if there is anything I can do.
--
Mike Kravetz
next prev parent reply other threads:[~2022-10-10 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 8:35 linux-next: Fixes tag needs some work in the mm-stable tree Stephen Rothwell
2022-10-09 9:15 ` Stephen Rothwell
2022-10-10 1:40 ` Mike Kravetz [this message]
2022-10-10 1:56 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2022-10-09 8:38 Stephen Rothwell
2022-10-09 8:36 Stephen Rothwell
2022-10-09 8:32 Stephen Rothwell
2022-09-12 5:45 Stephen Rothwell
2022-09-12 13:05 ` Wang, Haiyue
2022-09-12 18:55 ` 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=Y0N3/wtn3dR2h6TT@monkey \
--to=mike.kravetz@oracle$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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