From: cgel.zte@gmail.com
To: kvalo@kernel.org
Cc: cgel.zte@gmail.com, chi.minghao@zte.com.cn, davem@davemloft.net,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
wcn36xx@lists.infradead.org, zealci@zte.com.cn
Subject: Re: [PATCH V2] wcn36xx: use struct_size over open coded arithmetic
Date: Fri, 11 Feb 2022 01:29:54 +0000 [thread overview]
Message-ID: <20220211012954.1650997-1-chi.minghao@zte.com.cn> (raw)
In-Reply-To: <164449505175.11894.18378600637942439052.kvalo@kernel.org>
change log:
v1: msg_ind = kmalloc(struct_size(*msg_ind, msg, len), GFP_ATOMIC);
v2: msg_ind = kmalloc(struct_size(msg_ind, msg, len), GFP_ATOMIC);
thanks
Minghao
next prev parent reply other threads:[~2022-02-11 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 1:56 cgel.zte
2022-02-10 12:11 ` Kalle Valo
2022-02-11 1:29 ` cgel.zte [this message]
2022-02-14 17:51 ` Kalle Valo
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=20220211012954.1650997-1-chi.minghao@zte.com.cn \
--to=cgel.zte@gmail.com \
--cc=chi.minghao@zte.com.cn \
--cc=davem@davemloft.net \
--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=wcn36xx@lists.infradead.org \
--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
all inboxes | Powered by JetHome®