From: Peter Xu <peterx@redhat.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Alexey Dobriyan <adobriyan@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] docs: filesystem: Update smaps vm flag list to latest
Date: Mon, 1 Mar 2021 19:06:17 -0500 [thread overview]
Message-ID: <20210302000617.GJ397383@xz-x1> (raw)
In-Reply-To: <87v9aa1pue.fsf@meer.lwn.net>
On Mon, Mar 01, 2021 at 03:17:13PM -0700, Jonathan Corbet wrote:
> Peter Xu <peterx@redhat.com> writes:
>
> > We've missed a few documentation when adding new VM_* flags. Add the missing
> > pieces so they'll be in sync now.
> >
> > Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> > Documentation/filesystems/proc.rst | 5 +++++
> > 1 file changed, 5 insertions(+)
>
> So this patch doesn't apply; what version of the kernel did you generate
> it against? Could you redo against current kernels, please?
Sure. "mt" just got added, hence conflicted, but the rest are still missing.
Reposting. Thanks,
--
Peter Xu
prev parent reply other threads:[~2021-03-02 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 22:55 Peter Xu
2021-03-01 22:17 ` Jonathan Corbet
2021-03-02 0:06 ` Peter Xu [this message]
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=20210302000617.GJ397383@xz-x1 \
--to=peterx@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--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