From: Nishanth Menon <nm@ti.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: <kristo@kernel.org>, <ssantosh@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] firmware: ti_sci: Use devm_bitmap_zalloc when applicable
Date: Mon, 27 Sep 2021 08:38:07 -0500 [thread overview]
Message-ID: <20210927133807.rtkfjkxxlwpdqcnf@scouring> (raw)
In-Reply-To: <1bd77909ff75f62a2228a39db208c4c6d1b3e0e2.1632659746.git.christophe.jaillet@wanadoo.fr>
On 14:36-20210926, Christophe JAILLET wrote:
> 'xfer_alloc_table' is a bitmap. So use 'devm_bitmap_zalloc()' to simplify
> code and improve the semantic of the code.
>
> While at it, remove a redundant 'bitmap_zero()' call.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> drivers/firmware/ti_sci.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/firmware/ti_sci.c b/drivers/firmware/ti_sci.c
> index 235c7e7869aa..a33eb884102f 100644
> --- a/drivers/firmware/ti_sci.c
> +++ b/drivers/firmware/ti_sci.c
> @@ -3352,13 +3352,11 @@ static int ti_sci_probe(struct platform_device *pdev)
> if (!minfo->xfer_block)
> return -ENOMEM;
>
> - minfo->xfer_alloc_table = devm_kcalloc(dev,
> - BITS_TO_LONGS(desc->max_msgs),
> - sizeof(unsigned long),
> - GFP_KERNEL);
> + minfo->xfer_alloc_table = devm_bitmap_zalloc(dev,
> + desc->max_msgs,
> + GFP_KERNEL);
> if (!minfo->xfer_alloc_table)
> return -ENOMEM;
> - bitmap_zero(minfo->xfer_alloc_table, desc->max_msgs);
>
> /* Pre-initialize the buffer pointer to pre-allocated buffers */
> for (i = 0, xfer = minfo->xfer_block; i < desc->max_msgs; i++, xfer++) {
> --
> 2.30.2
>
Reviewed-by: Nishanth Menon <nm@ti.com>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-09-27 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 12:36 [PATCH] firmware: ti_sci: Use devm_bitmap_zalloc when applicable Christophe JAILLET
2021-09-27 13:38 ` Nishanth Menon [this message]
2022-10-31 20:40 ` Christophe JAILLET
2022-11-03 5:04 ` Nishanth Menon
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=20210927133807.rtkfjkxxlwpdqcnf@scouring \
--to=nm@ti.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ssantosh@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