From: Jens Axboe <axboe@kernel.dk>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>
Subject: Re: [PATCH][next] blk-iocost: Use struct_size() in kzalloc_node()
Date: Sat, 20 Jun 2020 15:25:08 -0600 [thread overview]
Message-ID: <e0afded8-386a-7619-a221-869ae2e606f6@kernel.dk> (raw)
In-Reply-To: <20200619230830.GA25608@embeddedor>
On 6/19/20 5:08 PM, Gustavo A. R. Silva wrote:
> Make use of the struct_size() helper instead of an open-coded version
> in order to avoid any potential type mistakes.
>
> This code was detected with the help of Coccinelle and, audited and
> fixed manually.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-06-20 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 23:08 [PATCH][next] blk-iocost: Use struct_size() in kzalloc_node() Gustavo A. R. Silva
2020-06-20 21:25 ` Jens Axboe [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=e0afded8-386a-7619-a221-869ae2e606f6@kernel.dk \
--to=axboe@kernel.dk \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).