From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: "kvalo@kernel.org" <kvalo@kernel.org>,
"cgel.zte@gmail.com" <cgel.zte@gmail.com>
Cc: "zealci@zte.com.cn" <zealci@zte.com.cn>,
"davem@davemloft.net" <davem@davemloft.net>,
"Berg, Johannes" <johannes.berg@intel.com>,
"chi.minghao@zte.com.cn" <chi.minghao@zte.com.cn>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"trix@redhat.com" <trix@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH v2] iwlwifi: dvm: use struct_size over open coded arithmetic
Date: Fri, 28 Jan 2022 12:34:10 +0000 [thread overview]
Message-ID: <9fde441c79a6f08ef3c99ded93a00d7bb15c9ac6.camel@intel.com> (raw)
In-Reply-To: <20220128093147.1213351-1-chi.minghao@zte.com.cn>
On Fri, 2022-01-28 at 09:31 +0000, cgel.zte@gmail.com wrote:
> From: Minghao Chi (CGEL ZTE) <chi.minghao@zte.com.cn>
>
> Replace zero-length array with flexible-array member and make use
> of the struct_size() helper in kmalloc(). For example:
You're not replacing zero-length arrays in this patch, so this is not
correct. Probably a copy/paste from a different patch?
--
Cheers,
Luca.
next prev parent reply other threads:[~2022-01-28 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 8:02 [PATCH] dvm: use struct_size over open coded arithmetic cgel.zte
2022-01-28 9:01 ` Kalle Valo
2022-01-28 9:31 ` [PATCH v2] iwlwifi: " cgel.zte
2022-01-28 12:34 ` Coelho, Luciano [this message]
2022-01-28 21:03 ` [PATCH] " kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2022-02-10 6:09 [PATCH V2] iwlwifi: " cgel.zte
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=9fde441c79a6f08ef3c99ded93a00d7bb15c9ac6.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=cgel.zte@gmail.com \
--cc=chi.minghao@zte.com.cn \
--cc=davem@davemloft.net \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=trix@redhat.com \
--cc=zealci@zte.com.cn \
/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).