From: David Miller <davem@davemloft.net>
To: keescook@chromium.org
Cc: saeedm@mellanox.com, tariqt@mellanox.com, leon@kernel.org,
vadimp@mellanox.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/mlx5: Use 2-factor allocator calls
Date: Mon, 09 Jul 2018 16:00:50 -0700 (PDT) [thread overview]
Message-ID: <20180709.160050.311196490781909931.davem@davemloft.net> (raw)
In-Reply-To: <20180704172847.GA33621@beast>
From: Kees Cook <keescook@chromium.org>
Date: Wed, 4 Jul 2018 10:28:47 -0700
> This restores the use of 2-factor allocation helpers that were already
> fixed treewide. Please do not use open-coded multiplication; prefer,
> instead, using 2-factor allocation helpers.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
Applied to net-next, thanks.
prev parent reply other threads:[~2018-07-09 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 17:28 [PATCH] net/mlx5: Use 2-factor allocator calls Kees Cook
2018-07-07 11:15 ` David Miller
2018-07-08 8:06 ` Leon Romanovsky
2018-07-08 8:12 ` Tariq Toukan
2018-07-09 23:00 ` David Miller [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=20180709.160050.311196490781909931.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=keescook@chromium.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=tariqt@mellanox.com \
--cc=vadimp@mellanox.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;
as well as URLs for NNTP newsgroup(s).