From: Andi Shyti <andi.shyti@kernel.org>
To: Triet Hoang <triet.hoang.dev@gmail.com>
Cc: bence98@sch.bme.hu, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] i2c: cp2615: handle allocation failure
Date: Fri, 28 Aug 2026 19:09:03 +0200 [thread overview]
Message-ID: <apG_qiYtTQvt9s-y@zenone.zhora.eu> (raw)
In-Reply-To: <20260818111703.19604-1-triet.hoang.dev@gmail.com>
Hi Triet,
thank you for your patch.
On Tue, Aug 18, 2026 at 11:17:01AM +0000, Triet Hoang wrote:
> Check the result of kzalloc_obj() and return -ENOMEM
> when the allocation fails instead of passing a NULL pointer
> to the message initialization helpers, which would return -EINVAL.
>
> Signed-off-by: Triet Hoang <triet.hoang.dev@gmail.com>
> ---
> Changes in v2:
> - Clarify the commit message to describe the actual behavior change.
> - Fix coding style regression
Next time please don't send your v2 as in reply to v1. It
confuses me.
> ---
> drivers/i2c/busses/i2c-cp2615.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/i2c/busses/i2c-cp2615.c b/drivers/i2c/busses/i2c-cp2615.c
> index 951de6249834..c1275fcad636 100644
> --- a/drivers/i2c/busses/i2c-cp2615.c
> +++ b/drivers/i2c/busses/i2c-cp2615.c
> @@ -128,6 +128,9 @@ cp2615_i2c_send(struct usb_interface *usbif, struct cp2615_i2c_transfer *i2c_w)
> struct usb_device *usbdev = interface_to_usbdev(usbif);
> int res = cp2615_init_i2c_msg(msg, i2c_w);
>
> + if (!msg)
> + return -ENOMEM;
> +
Your patch looks good, but, as you are at it, can I ask you here
a little effort? Personally I don't like and I find unreadable
the form:
struct cp2615_iop_msg *msg = kzalloc_obj(*msg);
...
if (!msg)
return -ENOMEM.
Important assignments, like kzalloc_*(), shouldn't be made during
declaration. I prefer the form:
struct cp2615_iop_msg *msg;
...
msg = kzalloc_obj(*msg);
if (!msg)
return -ENOMEM.
Works for you? Do you mind updating in v3?
Thanks,
Andi
> if (!res)
> res = usb_bulk_msg(usbdev, usb_sndbulkpipe(usbdev, IOP_EP_OUT),
> msg, ntohs(msg->length), NULL, 0);
next prev parent reply other threads:[~2026-08-28 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 16:17 [PATCH] i2c: cp2615: handle allocation failure Triet Hoang
2026-08-18 11:17 ` [PATCH v2] " Triet Hoang
2026-08-19 6:28 ` Markus Elfring
2026-08-28 12:08 ` Bence Csókás
2026-08-28 17:09 ` Andi Shyti
2026-08-28 20:12 ` Bence Csókás
2026-08-28 17:09 ` Andi Shyti [this message]
2026-08-28 20:40 ` Christophe JAILLET
2026-08-29 3:42 ` Triet Hoang
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=apG_qiYtTQvt9s-y@zenone.zhora.eu \
--to=andi.shyti@kernel.org \
--cc=bence98@sch.bme.hu \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=triet.hoang.dev@gmail.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