From: Andrew Morton <akpm@linux-foundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: AKASHI Takahiro <takahiro.akashi@linaro.org>,
Baoquan He <bhe@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org,
Wei Yang <richard.weiyang@gmail.com>
Subject: Re: [PATCH] resource: Use 2-factor allocator calls
Date: Thu, 5 Jul 2018 15:07:42 -0700 [thread overview]
Message-ID: <20180705150742.82f6efdf2cd8475a5d94e84a@linux-foundation.org> (raw)
In-Reply-To: <20180704173153.GA34386@beast>
On Wed, 4 Jul 2018 10:31:53 -0700 Kees Cook <keescook@chromium.org> wrote:
> As already done treewide, switch from open-coded multiplication to using
> 2-factor allocation helpers.
>
This is against resource-add-walk_system_ram_res_rev.patch
(http://lkml.kernel.org/r/20180322033722.9279-2-bhe@redhat.com).
That patch is awaiting (for several months!) a v2. Will this be happening?
next prev parent reply other threads:[~2018-07-05 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 17:31 [PATCH] resource: Use 2-factor allocator calls Kees Cook
2018-07-05 22:07 ` Andrew Morton [this message]
2018-07-06 1:14 ` Baoquan He
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=20180705150742.82f6efdf2cd8475a5d94e84a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weiyang@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=takahiro.akashi@linaro.org \
/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