From: Logan Gunthorpe <logang@deltatee.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
Rob Herring <robh@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org,
"Steven Rostedt \(VMware\)" <rostedt@goodmis.org>,
Russell King <linux@armlinux.org.uk>,
Philip Derrin <philip@cog.systems>,
Andrew Morton <akpm@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: mm: make use of new memblocks_present() helper
Date: Tue, 19 Mar 2019 15:12:44 -0600 [thread overview]
Message-ID: <7f590915-d35b-c46c-a05b-c368bf9c491c@deltatee.com> (raw)
In-Reply-To: <20190319210508.GD17966@rapoport-lnx>
On 2019-03-19 3:05 p.m., Mike Rapoport wrote:
>> You're probably referring to [1] which was for arm64 and was redundant
>> as my patch for that architecture was already picked up by Catalin.
>
> I've found the patch [1] I mentioned, and it was for ARM.
Ah, well, I wish knew I knew ahead of time that someone was doing my
work for me... My initial submission seemed to have been missed[1].
> AFAIK, For ARM you'd need to put it into Russel's patch tracking system [2].
Ah, I did not know this.
Logan
[1] https://lore.kernel.org/lkml/20190109202100.6968-2-logang@deltatee.com/
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-03-19 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 18:13 [PATCH] ARM: mm: make use of new memblocks_present() helper Logan Gunthorpe
2019-03-19 20:42 ` Mike Rapoport
2019-03-19 20:50 ` Logan Gunthorpe
2019-03-19 21:05 ` Mike Rapoport
2019-03-19 21:12 ` Logan Gunthorpe [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=7f590915-d35b-c46c-a05b-c368bf9c491c@deltatee.com \
--to=logang@deltatee.com \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nicolas.pitre@linaro.org \
--cc=philip@cog.systems \
--cc=robh@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rppt@linux.ibm.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