From: akpm@linux-foundation.org (Andrew Morton)
To: linux-riscv@lists.infradead.org
Subject: [PATCH 2/2] mm/sparse: add common helper to mark all memblocks present
Date: Wed, 7 Nov 2018 12:38:38 -0800 [thread overview]
Message-ID: <20181107123838.1b7234c98a87dec5a2b25e67@linux-foundation.org> (raw)
In-Reply-To: <b1cc442e-7314-4a8e-3eec-9adc200d7582@deltatee.com>
On Wed, 7 Nov 2018 13:36:34 -0700 Logan Gunthorpe <logang@deltatee.com> wrote:
> > Actually if both names suck, then there also is the option to rename both
> > instead of adding a comment to explain the suckage.
>
> Ok, well, I wasn't expecting to take on a big rename like that as it
> would create a patch touching a bunch of arches and mm files... But if
> we can come to some agreement on a better name and someone is willing to
> take that patch without significant delay then I'd be happy to create
> the patch and add it to the start of my series.
Some other time ;) Let's just get the missing documentation added for now?
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: linux-arch@vger.kernel.org, Albert Ou <aou@eecs.berkeley.edu>,
Arnd Bergmann <arnd@arndb.de>,
linux-sh@vger.kernel.org, Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org, Stephen Bates <sbates@raithlin.com>,
linux-mm@kvack.org, Michal Hocko <mhocko@suse.com>,
Vlastimil Babka <vbabka@suse.cz>,
Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@lst.de>,
linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH 2/2] mm/sparse: add common helper to mark all memblocks present
Date: Wed, 7 Nov 2018 12:38:38 -0800 [thread overview]
Message-ID: <20181107123838.1b7234c98a87dec5a2b25e67@linux-foundation.org> (raw)
Message-ID: <20181107203838.k3Wxhjb8kbXyZshdgpWdyIxE6lqlA3dWdNufijfL09s@z> (raw)
In-Reply-To: <b1cc442e-7314-4a8e-3eec-9adc200d7582@deltatee.com>
On Wed, 7 Nov 2018 13:36:34 -0700 Logan Gunthorpe <logang@deltatee.com> wrote:
> > Actually if both names suck, then there also is the option to rename both
> > instead of adding a comment to explain the suckage.
>
> Ok, well, I wasn't expecting to take on a big rename like that as it
> would create a patch touching a bunch of arches and mm files... But if
> we can come to some agreement on a better name and someone is willing to
> take that patch without significant delay then I'd be happy to create
> the patch and add it to the start of my series.
Some other time ;) Let's just get the missing documentation added for now?
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-11-07 20:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 17:38 [PATCH 0/2] Introduce common code for risc-v sparsemem support Logan Gunthorpe
2018-11-07 17:38 ` Logan Gunthorpe
2018-11-07 17:38 ` [PATCH 1/2] mm: Introduce common STRUCT_PAGE_MAX_SHIFT define Logan Gunthorpe
2018-11-07 17:38 ` Logan Gunthorpe
2018-11-07 20:11 ` Andrew Morton
2018-11-07 20:11 ` Andrew Morton
2018-11-07 17:38 ` [PATCH 2/2] mm/sparse: add common helper to mark all memblocks present Logan Gunthorpe
2018-11-07 17:38 ` Logan Gunthorpe
2018-11-07 20:12 ` Andrew Morton
2018-11-07 20:12 ` Andrew Morton
2018-11-07 20:19 ` Logan Gunthorpe
2018-11-07 20:19 ` Logan Gunthorpe
2018-11-07 20:26 ` Thomas Gleixner
2018-11-07 20:26 ` Thomas Gleixner
2018-11-07 20:36 ` Logan Gunthorpe
2018-11-07 20:36 ` Logan Gunthorpe
2018-11-07 20:38 ` Andrew Morton [this message]
2018-11-07 20:38 ` Andrew Morton
2018-11-07 20:56 ` Thomas Gleixner
2018-11-07 20:56 ` Thomas Gleixner
2018-12-06 17:40 ` Logan Gunthorpe
2018-12-07 19:56 ` Andrew Morton
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=20181107123838.1b7234c98a87dec5a2b25e67@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-riscv@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).