From: Christoph Hellwig <hch@infradead.org>
To: Rob Herring <robh@kernel.org>
Cc: Rich Felker <dalias@libc.org>,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: [PATCH] sh: switch to NO_BOOTMEM
Date: Mon, 14 May 2018 12:03:43 +0000 [thread overview]
Message-ID: <20180514120343.GB5265@infradead.org> (raw)
In-Reply-To: <20180511134559.13464-1-robh@kernel.org>
> unflattening could also fix this, but removing bootmem is desired. So
> enable NO_BOOTMEM on SH like other architectures have done.
Can you send out similarly shoot in the wild conversion for the
remaining architectures while you are at it? We still seem to be
missing: alpha, c6x, hexagon, ia64, m68k, mips, nios2 and unicore32.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Rob Herring <robh@kernel.org>
Cc: Rich Felker <dalias@libc.org>,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: [PATCH] sh: switch to NO_BOOTMEM
Date: Mon, 14 May 2018 05:03:43 -0700 [thread overview]
Message-ID: <20180514120343.GB5265@infradead.org> (raw)
In-Reply-To: <20180511134559.13464-1-robh@kernel.org>
> unflattening could also fix this, but removing bootmem is desired. So
> enable NO_BOOTMEM on SH like other architectures have done.
Can you send out similarly shoot in the wild conversion for the
remaining architectures while you are at it? We still seem to be
missing: alpha, c6x, hexagon, ia64, m68k, mips, nios2 and unicore32.
next prev parent reply other threads:[~2018-05-14 12:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 13:45 [PATCH] sh: switch to NO_BOOTMEM Rob Herring
2018-05-11 13:45 ` Rob Herring
2018-05-11 15:02 ` Rich Felker
2018-05-11 15:02 ` Rich Felker
2018-05-11 15:37 ` Rob Herring
2018-05-11 15:37 ` Rob Herring
2018-05-11 15:55 ` Rich Felker
2018-05-11 15:55 ` Rich Felker
2018-05-14 12:03 ` Christoph Hellwig [this message]
2018-05-14 12:03 ` Christoph Hellwig
2018-05-14 20:01 ` Rob Herring
2018-05-14 20:01 ` Rob Herring
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=20180514120343.GB5265@infradead.org \
--to=hch@infradead.org \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.