mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
	<linux@armlinux.org.uk>, Atish Patra <Atish.Patra@wdc.com>,
	<guoren@kernel.org>, Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH v2] initramfs: Provide a common initrd reserve function
Date: Fri, 15 Jan 2021 13:44:42 +0800	[thread overview]
Message-ID: <6ad30931-85a1-37a1-ce80-9a8752ebb22a@huawei.com> (raw)
In-Reply-To: <mhng-68a3f8a1-02f5-4487-ae17-fc06c81f072c@penguin>


On 2021/1/15 10:33, Palmer Dabbelt wrote:
> On Wed, 13 Jan 2021 18:33:58 PST (-0800), wangkefeng.wang@huawei.com 
> wrote:
>> The ARM and riscv have same logic to check and reserve
>> the memory of initrd, let's provide a common function to
>> reduce duplicated code.
>>
>> Add __LINUX_INITRD_H define in initrd.h to prevent build error
>> (found by kernel test robot <lkp@intel.com>) from the multiple
>> inclusion of same header file multiple time.
>
> This is doing a bunch of different things:
>
> * Fixing the lack of a preprocessor guard in initrd.h
> * Adding some generic code.
> * Converting two architectures over to that generic code.
>
> It needs to be split into four patches.  I'm happy to take them via 
> the RISC-V tree (with an Ack from for the arch/arm/ stuff), but not 
> all together.
>
> It looks like csky copied this as well, they at least have exactly the 
> same message.

Send v3, according to the suggestion,thanks.


      reply	other threads:[~2021-01-15  5:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14  2:33 Kefeng Wang
2021-01-15  2:33 ` Palmer Dabbelt
2021-01-15  5:44   ` Kefeng Wang [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=6ad30931-85a1-37a1-ce80-9a8752ebb22a@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=Atish.Patra@wdc.com \
    --cc=guoren@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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

all inboxes | Powered by JetHome®