From: Andrew Morton <akpm@linux-foundation.org>
To: Liam Howlett <liam.howlett@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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: Wed, 27 Apr 2022 20:09:26 -0700 [thread overview]
Message-ID: <20220427200926.bd22f6b77eb1fa601a56d9ec@linux-foundation.org> (raw)
In-Reply-To: <20220428023743.qaxoj7nrrp5buixn@revolver>
On Thu, 28 Apr 2022 02:37:53 +0000 Liam Howlett <liam.howlett@oracle.com> wrote:
> * Stephen Rothwell <sfr@canb.auug.org.au> [220427 18:42]:
> > Hi all,
> >
> > In commit
> >
> > bc7608890065 ("mm/mlock: use maple state in apply_mlockall_flags()")
> >
> > Fixes tag
> >
> > Fixes: 0d43186b36c1 (mm/mlock: use vma iterator and instead of vma linked list)
> >
> > has these problem(s):
> >
> > - Target SHA1 does not exist
> >
> > Maybe you meant
> >
> > Fixes: 1dfcb33e7c19 ("mm/mlock: use vma iterator and instead of vma linked list")
>
> I did.
>
> >
> > This is a semi-automatic notification - I know this is just a fix patch
> > that will probably be rolled into the patch it fixes.
>
> I'm sorry but there will most likely be more of these since I used a
> side branch for my fixes today.
I dunno about all of this. My approach to SHA1 shortening is to lean
on the backspace key until it looks about right (circa 1.5" in metric),
then ship it.
How about we simply turn this off?
next prev parent reply other threads:[~2022-04-28 3:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 22:42 linux-next: Fixes tag needs some work in the mm tree Stephen Rothwell
2022-04-28 2:37 ` Liam Howlett
2022-04-28 3:09 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-13 6:56 Stephen Rothwell
2022-05-25 0:27 Stephen Rothwell
2022-05-25 0:36 ` Zi Yan
2022-06-30 3:32 Stephen Rothwell
2022-06-30 15:20 ` Liam Howlett
2022-06-30 3:37 Stephen Rothwell
2022-06-30 15:28 ` Liam Howlett
2022-06-30 18:16 ` Andrew Morton
2022-07-26 23:23 Stephen Rothwell
2022-07-27 0:02 ` Andrew Morton
2022-09-18 22:21 Stephen Rothwell
2022-09-19 14:47 ` Zach O'Keefe
2022-09-19 21:04 ` Andrew Morton
2022-09-21 18:24 ` Zach O'Keefe
2022-11-23 22:00 Stephen Rothwell
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
2023-10-10 5:47 Stephen Rothwell
2023-10-10 15:42 ` Zi Yan
2023-10-17 4:33 Stephen Rothwell
2023-12-12 20:59 Stephen Rothwell
2023-12-13 1:04 ` Andrew Morton
2024-02-04 21:29 Stephen Rothwell
2024-02-25 21:18 Stephen Rothwell
2024-07-09 22:54 Stephen Rothwell
2025-02-09 6:22 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=20220427200926.bd22f6b77eb1fa601a56d9ec@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=liam.howlett@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox