From: Hugh Dickins <hughd@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH mmotm 00/15] mm: assorted small fixes and cleanups
Date: Wed, 2 Mar 2022 17:30:27 -0800 (PST) [thread overview]
Message-ID: <8caa60fa-fb3e-e2ea-64fa-65971e382db9@google.com> (raw)
Andrew, I'm about to trickle through the first six of probably fifteen
patches, diffed against against top of next-20220301, equally applicable
to mmotm 2022-02-28-14-45 (sorry, not looked at 2022-03-02-16-53 yet).
These are independent patches, which may be applied or dropped as you
wish: I'm not numbering them N/15, and I'm Cc'ing different interested
parties on the different patches.
More to come later today or tomorrow or after, I'm still updating
commit messages and Cc-lists for the rebased and retested patches: many
of which go back years, never quite reaching priority for posting until
now. I'd hoped to send them earlier in the cycle, but mm/munlock took
precedence - and the first I'll send is a fix to an issue there.
Thanks,
Hugh
next reply other threads:[~2022-03-03 1:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 1:30 Hugh Dickins [this message]
2022-03-05 5:15 ` Hugh Dickins
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=8caa60fa-fb3e-e2ea-64fa-65971e382db9@google.com \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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