All of lore.kernel.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@sifive.com>
To: logang@deltatee.com
Cc: robh@kernel.org, dalias@libc.org, ysato@users.sourceforge.jp,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	sbates@raithlin.com, Christoph Hellwig <hch@infradead.org>,
	dan.j.williams@intel.com, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper
Date: Thu, 21 Mar 2019 01:37:12 -0700 (PDT)	[thread overview]
Message-ID: <mhng-79bcf945-38aa-4ca5-82d2-eaa5b1286175@palmer-si-x1c4> (raw)
In-Reply-To: <9ac29b0d-4c25-3f5c-3812-44b42332447d@deltatee.com>

On Wed, 20 Mar 2019 10:43:09 PDT (-0700), logang@deltatee.com wrote:
>
>
> On 2019-03-19 8:54 p.m., Palmer Dabbelt wrote:
>> On Tue, 19 Mar 2019 10:56:52 PDT (-0700), logang@deltatee.com wrote:
>>> Hey Palmer,
>>>
>>> On 2019-01-23 12:56 p.m., Palmer Dabbelt wrote:
>>>>> @Palmer: if you can just look at taking the second patch, I'll resubmit
>>>>> the first one to the appropriate list.
>>>>
>>>> Works for me.  I'll queue the second patch into my staging branch, targeted for
>>>> the next merge window.
>>>
>>> It doesn't look like my sparesmem patch made it into v5.1-rc1. Did it
>>> fall through the cracks?
>>
>> It must have, sorry.  Is this what you're referring to?
>>
>>     https://patchwork.kernel.org/patch/10754911/
>
> Yes, though it conflicts with v5.1-rc1 due to some code reorganization.
>
> I've updated it and we will submit it later this week as part of a
> larger patch set which helps enable p2p on RISC-V.

Thanks!

WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@sifive.com>
To: logang@deltatee.com
Cc: robh@kernel.org, dalias@libc.org, ysato@users.sourceforge.jp,
	linux-kernel@vger.kernel.org, sbates@raithlin.com,
	Christoph Hellwig <hch@infradead.org>,
	linux-riscv@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
	dan.j.williams@intel.com
Subject: Re: [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper
Date: Thu, 21 Mar 2019 01:37:12 -0700 (PDT)	[thread overview]
Message-ID: <mhng-79bcf945-38aa-4ca5-82d2-eaa5b1286175@palmer-si-x1c4> (raw)
In-Reply-To: <9ac29b0d-4c25-3f5c-3812-44b42332447d@deltatee.com>

On Wed, 20 Mar 2019 10:43:09 PDT (-0700), logang@deltatee.com wrote:
>
>
> On 2019-03-19 8:54 p.m., Palmer Dabbelt wrote:
>> On Tue, 19 Mar 2019 10:56:52 PDT (-0700), logang@deltatee.com wrote:
>>> Hey Palmer,
>>>
>>> On 2019-01-23 12:56 p.m., Palmer Dabbelt wrote:
>>>>> @Palmer: if you can just look at taking the second patch, I'll resubmit
>>>>> the first one to the appropriate list.
>>>>
>>>> Works for me.  I'll queue the second patch into my staging branch, targeted for
>>>> the next merge window.
>>>
>>> It doesn't look like my sparesmem patch made it into v5.1-rc1. Did it
>>> fall through the cracks?
>>
>> It must have, sorry.  Is this what you're referring to?
>>
>>     https://patchwork.kernel.org/patch/10754911/
>
> Yes, though it conflicts with v5.1-rc1 due to some code reorganization.
>
> I've updated it and we will submit it later this week as part of a
> larger patch set which helps enable p2p on RISC-V.

Thanks!

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

  reply	other threads:[~2019-03-21  8:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 19:56 [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper Palmer Dabbelt
2019-01-23 19:56 ` Palmer Dabbelt
2019-01-23 20:31 ` Logan Gunthorpe
2019-01-23 20:31   ` Logan Gunthorpe
2019-03-19 17:56 ` Logan Gunthorpe
2019-03-19 17:56   ` Logan Gunthorpe
2019-03-20  2:54   ` Palmer Dabbelt
2019-03-20  2:54     ` Palmer Dabbelt
2019-03-20 17:43     ` Logan Gunthorpe
2019-03-20 17:43       ` Logan Gunthorpe
2019-03-21  8:37       ` Palmer Dabbelt [this message]
2019-03-21  8:37         ` Palmer Dabbelt
  -- strict thread matches above, loose matches on Subject: below --
2019-01-09 20:39 [PATCH v4 0/2] [PATCH v2 0/6] sparsemem support for RISC-V Logan Gunthorpe
2019-01-09 20:39 ` [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper Logan Gunthorpe
2019-01-09 20:39   ` Logan Gunthorpe
2019-01-15 13:58   ` Christoph Hellwig
2019-01-15 13:58     ` Christoph Hellwig
2019-01-15 17:30     ` Logan Gunthorpe
2019-01-15 17:30       ` Logan Gunthorpe

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=mhng-79bcf945-38aa-4ca5-82d2-eaa5b1286175@palmer-si-x1c4 \
    --to=palmer@sifive.com \
    --cc=dalias@libc.org \
    --cc=dan.j.williams@intel.com \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=logang@deltatee.com \
    --cc=robh@kernel.org \
    --cc=sbates@raithlin.com \
    --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.