From: Jakub Kicinski <kuba@kernel.org>
To: Julia Lawall <Julia.Lawall@inria.fr>
Cc: Veerasenareddy Burru <vburru@marvell.com>,
keescook@chromium.org, kernel-janitors@vger.kernel.org,
Abhijit Ayarekar <aayarekar@marvell.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/26] octeon_ep: use array_size
Date: Sat, 24 Jun 2023 15:28:26 -0700 [thread overview]
Message-ID: <20230624152826.10e3789b@kernel.org> (raw)
In-Reply-To: <20230623211457.102544-3-Julia.Lawall@inria.fr>
On Fri, 23 Jun 2023 23:14:33 +0200 Julia Lawall wrote:
> - oq->buff_info = vzalloc(oq->max_count * OCTEP_OQ_RECVBUF_SIZE);
> + oq->buff_info = vzalloc(array_size(oq->max_count, OCTEP_OQ_RECVBUF_SIZE));
vcalloc seems to exist, is there a reason array_size() is preferred?
--
pw-bot: cr
next prev parent reply other threads:[~2023-06-24 22:28 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 21:14 [PATCH 00/26] use array_size Julia Lawall
2023-06-23 21:14 ` [PATCH 01/26] lib/test_vmalloc.c: " Julia Lawall
2023-06-23 21:14 ` [PATCH 02/26] octeon_ep: " Julia Lawall
2023-06-24 15:46 ` Simon Horman
2023-06-24 22:28 ` Jakub Kicinski [this message]
2023-06-25 20:14 ` Christophe JAILLET
2023-06-25 20:25 ` Julia Lawall
2023-06-25 20:32 ` Christophe JAILLET
2023-06-25 20:57 ` Julia Lawall
2023-06-23 21:14 ` [PATCH 03/26] drm/gud: " Julia Lawall
2023-06-23 21:14 ` [PATCH 04/26] gve: " Julia Lawall
2023-06-24 15:47 ` Simon Horman
2023-06-23 21:14 ` [PATCH 05/26] RDMA/erdma: " Julia Lawall
2023-06-27 9:32 ` Cheng Xu
2023-06-23 21:14 ` [PATCH 06/26] dma-buf: system_heap: " Julia Lawall
2023-06-23 21:42 ` John Stultz
2023-06-23 21:14 ` [PATCH 07/26] scsi: fnic: " Julia Lawall
2023-06-23 21:14 ` [PATCH 08/26] virtio-mem: " Julia Lawall
2023-06-25 1:39 ` Xuan Zhuo
2023-06-26 7:40 ` David Hildenbrand
2023-06-26 10:59 ` Michael S. Tsirkin
2023-06-23 21:14 ` [PATCH 09/26] pds_core: " Julia Lawall
2023-06-24 15:47 ` Simon Horman
2023-06-26 16:02 ` Shannon Nelson
2023-06-23 21:14 ` [PATCH 10/26] bus: mhi: host: " Julia Lawall
2023-06-23 21:30 ` Jeffrey Hugo
2023-06-23 21:45 ` Julia Lawall
2023-06-23 22:09 ` Jeffrey Hugo
2023-06-23 23:45 ` Kees Cook
2023-06-24 16:06 ` Jeffrey Hugo
2023-06-26 11:46 ` Dan Carpenter
2023-06-26 14:53 ` Jeffrey Hugo
2023-06-23 21:14 ` [PATCH 11/26] ionic: " Julia Lawall
2023-06-24 15:47 ` Simon Horman
2023-06-26 16:03 ` Shannon Nelson
2023-06-23 21:14 ` [PATCH 12/26] btrfs: zoned: " Julia Lawall
2023-06-26 6:08 ` Johannes Thumshirn
2023-06-26 7:59 ` Naohiro Aota
2023-06-29 14:30 ` David Sterba
2023-06-23 21:14 ` [PATCH 13/26] iommu/tegra: gart: " Julia Lawall
2023-06-23 21:14 ` [PATCH 14/26] RDMA/siw: " Julia Lawall
2023-06-26 11:23 ` Bernard Metzler
2023-06-23 21:14 ` [PATCH 15/26] habanalabs: " Julia Lawall
2023-06-23 21:14 ` [PATCH 16/26] drm/i915/gvt: " Julia Lawall
2023-06-26 9:26 ` [Intel-gfx] " Andi Shyti
2023-06-26 11:54 ` Dan Carpenter
2023-06-23 21:14 ` [PATCH 17/26] kcov: " Julia Lawall
2023-06-24 5:34 ` Dmitry Vyukov
2023-06-23 21:14 ` [PATCH 18/26] net: enetc: " Julia Lawall
2023-06-24 15:48 ` Simon Horman
2023-06-23 21:14 ` [PATCH 19/26] RDMA/bnxt_re: " Julia Lawall
2023-06-23 21:14 ` [PATCH 20/26] drm/vmwgfx: " Julia Lawall
2023-06-27 17:33 ` Julia Lawall
2023-06-23 21:14 ` [PATCH 21/26] x86/sgx: " Julia Lawall
2023-07-10 22:02 ` Jarkko Sakkinen
2023-06-23 21:14 ` [PATCH 22/26] net: mana: " Julia Lawall
2023-06-24 15:48 ` Simon Horman
2023-06-23 21:14 ` [PATCH 23/26] media: staging: imgu: " Julia Lawall
2023-06-25 4:59 ` Bingbu Cao
2023-06-27 17:35 ` Julia Lawall
2023-06-29 7:34 ` Sakari Ailus
2023-06-23 21:14 ` [PATCH 24/26] scsi: qla2xxx: " Julia Lawall
2023-06-23 21:14 ` [PATCH 25/26] vduse: " Julia Lawall
2023-06-23 21:14 ` [PATCH 26/26] comedi: " Julia Lawall
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=20230624152826.10e3789b@kernel.org \
--to=kuba@kernel.org \
--cc=Julia.Lawall@inria.fr \
--cc=aayarekar@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vburru@marvell.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