From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Xu Yu <xuyu@linux.alibaba.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: Thu, 28 Apr 2022 08:36:04 +1000 [thread overview]
Message-ID: <20220428083604.0872e25a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
Hi all,
In commit
9d4dacd9cc3f ("Revert "mm/memory-failure.c: skip huge_zero_page in memory_failure()"")
Fixes tag
Fixes: d173d5417fb ("mm/memory-failure.c: skip huge_zero_page in memory_failure()")
has these problem(s):
- SHA1 should be at least 12 digits long
In commit
7b5cc291112f ("mm/huge_memory: do not overkill when splitting huge_zero_page")
Fixes tag
Fixes: d173d5417fb ("mm/memory-failure.c: skip huge_zero_page in memory_failure()")
has these problem(s):
- SHA1 should be at least 12 digits long
These are probably not worth rebasing for but this can be fixed for the
future 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").
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-04-27 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 22:36 Stephen Rothwell [this message]
2022-08-07 21:19 linux-next: Fixes tag needs some work in the mm-hotfixes tree Stephen Rothwell
2022-08-07 23:01 ` Peter Xu
2023-06-07 4:35 Stephen Rothwell
2023-11-29 20:43 Stephen Rothwell
2023-11-30 1:07 ` Baoquan He
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=20220428083604.0872e25a@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=xuyu@linux.alibaba.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.