All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Atish Patra <Atish.Patra@wdc.com>,
	linux-riscv@lists.infradead.org,
	Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH v2] riscv: Cleanup setup_bootmem()
Date: Sat, 27 Feb 2021 09:21:00 +0800	[thread overview]
Message-ID: <ac23c2d9-f102-00be-25d9-b05712f17ee0@huawei.com> (raw)
In-Reply-To: <mhng-b8acf3e5-d496-4094-8b55-c7a6d5fa2dc5@palmerdabbelt-glaptop>


On 2021/2/19 15:15, Palmer Dabbelt wrote:
> On Mon, 08 Feb 2021 17:01:51 PST (-0800), wangkefeng.wang@huawei.com 
> wrote:
>> After the following patches,
>>
>>   commit de043da0b9e7 ("RISC-V: Fix usage of 
>> memblock_enforce_memory_limit")
>>   commit 1bd14a66ee52 ("RISC-V: Remove any memblock representing 
>> unusable memory area")
>>   commit b10d6bca8720 ("arch, drivers: replace for_each_membock() 
>> with for_each_mem_range()")
>>
>> some logic is useless, kill the mem_start/start/end and unneeded code.
>>
>> Reviewed-by: Atish Patra <atish.patra@wdc.com>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>>
...
>
> Thanks, this is on for-next.
Hi Palmer, maybe this one is missed?
> .
>

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2021-02-27  1:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09  1:01 [PATCH v2] riscv: Cleanup setup_bootmem() Kefeng Wang
2021-02-19  7:15 ` Palmer Dabbelt
2021-02-27  1:21   ` Kefeng Wang [this message]
2021-02-27  5:26     ` Palmer Dabbelt

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=ac23c2d9-f102-00be-25d9-b05712f17ee0@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=Atish.Patra@wdc.com \
    --cc=linux-riscv@lists.infradead.org \
    --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 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.