From: Andrew Morton <akpm@linux-foundation.org>
To: Miles Chen <miles.chen@mediatek.com>
Cc: <adobriyan@gmail.com>, <andreyknvl@google.com>,
<aryabinin@virtuozzo.com>, <catalin.marinas@arm.com>,
<dvyukov@google.com>, <ebiederm@xmission.com>, <elver@google.com>,
<glider@google.com>, <mm-commits@vger.kernel.org>,
<song.bao.hua@hisilicon.com>, <stable@vger.kernel.org>,
<vincenzo.frascino@arm.com>, <will.deacon@arm.com>
Subject: Re: + proc-use-untagged_addr-for-pagemap_read-addresses.patch added to -mm tree
Date: Wed, 2 Dec 2020 15:34:02 -0800 [thread overview]
Message-ID: <20201202153402.4b157e9a4f19e7f932a7cf68@linux-foundation.org> (raw)
In-Reply-To: <1606874629.22275.5.camel@mtkswgap22>
On Wed, 2 Dec 2020 10:03:49 +0800 Miles Chen <miles.chen@mediatek.com> wrote:
> On Fri, 2020-11-27 at 19:52 -0800, akpm@linux-foundation.org wrote:
> > The patch titled
> > Subject: proc: use untagged_addr() for pagemap_read addresses
> > has been added to the -mm tree. Its filename is
> > proc-use-untagged_addr-for-pagemap_read-addresses.patch
> >
> > This patch should soon appear at
> > https://ozlabs.org/~akpm/mmots/broken-out/proc-use-untagged_addr-for-pagemap_read-addresses.patch
> > and later at
> > https://ozlabs.org/~akpm/mmotm/broken-out/proc-use-untagged_addr-for-pagemap_read-addresses.patch
> >
> > Before you just go and hit "reply", please:
> > a) Consider who else should be cc'ed
> > b) Prefer to cc a suitable mailing list as well
> > c) Ideally: find the original patch on the mailing list and do a
> > reply-to-all to that, adding suitable additional cc's
> >
> > *** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
> >
> > The -mm tree is included into linux-next and is updated
> > there every 3-4 working days
>
> Sorry for bothering, I checked the next-20201201 tag and the patch in
> next-20201201 is [1], but there is a overflow issue in [1] so I
> submitted v2 [2]. We should take [2], right?
> (the patch in this email is [2] but the patch in next-20201201 is [1])
>
> [1] https://lore.kernel.org/patchwork/patch/1343258/
> [1] https://lore.kernel.org/patchwork/patch/1345874/
>
Yup, I haven't released an -mm snapshot since updating to v2. (Been
waiting for an arm64 situation to settle itself out). Hopefully
today...
next prev parent reply other threads:[~2020-12-02 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 3:52 + proc-use-untagged_addr-for-pagemap_read-addresses.patch added to -mm tree akpm
2020-12-02 2:03 ` Miles Chen
2020-12-02 23:34 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-05 5:23 akpm
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=20201202153402.4b157e9a4f19e7f932a7cf68@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=miles.chen@mediatek.com \
--cc=mm-commits@vger.kernel.org \
--cc=song.bao.hua@hisilicon.com \
--cc=stable@vger.kernel.org \
--cc=vincenzo.frascino@arm.com \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox