From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: David Hildenbrand <david@redhat.com>
Cc: Wesley Zhao <zhaowei1102@thundersoft.com>,
akpm@linux-foundation.org, keescook@chromium.org,
tglx@linutronix.de, kerneldev@karsmulder.nl,
nivedita@alum.mit.edu, joe@perches.com, gpiccoli@canonical.com,
aquini@redhat.com, gustavoars@kernel.org, ojeda@kernel.org,
linux-kernel@vger.kernel.org, dan.j.williams@intel.com,
guohanjun@huawei.com, mchehab+huawei@kernel.org
Subject: Re: [PATCH 2/2] resource: Make it possible to reserve memory on 64bit platform
Date: Mon, 11 Jan 2021 20:03:30 +0200 [thread overview]
Message-ID: <20210111180330.GA4077@smile.fi.intel.com> (raw)
In-Reply-To: <0043f2fe-d936-0db6-7b12-25a5026cb106@redhat.com>
On Mon, Jan 11, 2021 at 06:24:35PM +0100, David Hildenbrand wrote:
> On 11.01.21 17:33, Wesley Zhao wrote:
> > From: "Wesley.Zhao" <zhaowei1102@thundersoft.com>
> >
> > For now "reserve=" is limitied to 32bit,not available on 64bit
> > platform,so we change the get_option() to get_option_ull(added in
> > patch: commit 4b6bfe96265e ("lib/cmdline: add new function
> > get_option_ull()"))
>
> Curious, what's the target use case? (did not receive a cover letter,
> maybe it's buried in there)
Oh, I didn't received neither cover letter nor patch 2!
To author: please, address comments to patch 1 along with (re)sending cover
letter and include every stakeholder to the entire series.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-01-11 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 16:33 [PATCH 1/2] lib/cmdline: add new function get_option_ull() Wesley Zhao
2021-01-11 16:33 ` [PATCH 2/2] resource: Make it possible to reserve memory on 64bit platform Wesley Zhao
2021-01-11 17:24 ` David Hildenbrand
2021-01-11 18:03 ` Andy Shevchenko [this message]
2021-01-11 17:22 ` [PATCH 1/2] lib/cmdline: add new function get_option_ull() Andy Shevchenko
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=20210111180330.GA4077@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=aquini@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=gpiccoli@canonical.com \
--cc=guohanjun@huawei.com \
--cc=gustavoars@kernel.org \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=kerneldev@karsmulder.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nivedita@alum.mit.edu \
--cc=ojeda@kernel.org \
--cc=tglx@linutronix.de \
--cc=zhaowei1102@thundersoft.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.