Linux I2C development
 help / color / mirror / Atom feed
From: "Bence Csókás" <bence98@sch.bme.hu>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: "Triet Hoang" <triet.hoang.dev@gmail.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Markus Elfring" <Markus.Elfring@web.de>,
	kernel-janitors@vger.kernel.org,
	"Bence Csókás" <bence98@sch.bme.hu>
Subject: Re: [PATCH v2] i2c: cp2615: handle allocation failure
Date: Fri, 28 Aug 2026 22:12:26 +0200	[thread overview]
Message-ID: <d3840605-a5f5-4b27-83b4-98aef6e7fc89@sch.bme.hu> (raw)
In-Reply-To: <apHAu8HnMD14c_Au@zenone.zhora.eu>

Hi,

On 8/28/26 19:09, Andi Shyti wrote:
> On Fri, Aug 28, 2026 at 02:08:19PM +0200, Bence Csókás wrote:
>> On 8/19/26 08:28, Markus Elfring wrote:
>>> * How do you think about to increase the application of scope-based
>> resource management?
>>
>> I second this, this old code could use some RAII modernization.
> 
> is there a managed version for kzalloc_obj()?
Well I'm thinking, since msg's lifetime is only within the functions, it 
can be attributed with `__free(kfree)`.

Anyways, in the curent state of this patch, I'm afraid I must NAK it.

Bence

  reply	other threads:[~2026-08-28 20:12 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 [this message]
2026-08-28 17:09   ` Andi Shyti
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=d3840605-a5f5-4b27-83b4-98aef6e7fc89@sch.bme.hu \
    --to=bence98@sch.bme.hu \
    --cc=Markus.Elfring@web.de \
    --cc=andi.shyti@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --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