Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Jonathan Cameron <jic23@jic23.retrosnub.co.uk>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Jonathan Cameron <jic23@kernel.org>, <linux-iio@vger.kernel.org>
Subject: Re: [RFC PATCH 01/13] device property: Add cleanup.h based fwnode_handle_put() scope based cleanup.
Date: Mon, 8 Jan 2024 12:51:17 +0000	[thread overview]
Message-ID: <20240108125117.000010fb@Huawei.com> (raw)
In-Reply-To: <4b6f283d-48b9-4702-81dc-003a2dcfc3f1@rasmusvillemoes.dk>

On Sun, 7 Jan 2024 22:05:35 +0100
Rasmus Villemoes <linux@rasmusvillemoes.dk> wrote:

> On 06/01/2024 18.53, Jonathan Cameron wrote:
> > 
> > ething similar and PeterZ explained there why if (_T) is  
> >> important, hence this should be  
> > 
> > I can't find the reference unfortunately. 
> >   
> >>
> >> DEFINE_FREE(fwnode_handle, struct fwnode_handle *, if (_T) fwnode_handle_put(_T))
> >>
> >> or even
> >>
> >> DEFINE_FREE(fwnode_handle, struct fwnode_handle *, if (!IS_ERR_OR_NULL(_T)) fwnode_handle_put(_T))
> >>
> >> as we accept in many calls an error pointer as unset / undefined firmware node
> >> handle.  
> > 
> > The function called has a protection for null
> >  and error inputs so I'm not sure why extra protection
> > is needed?  
> 
> IIRC, it's for code generation, avoiding emitting the call to the
> cleanup function on the code paths where the compiler knows the argument
> is NULL. And on the other return paths, the compiler most likely knows
> the value is non-NULL, so the conditional is elided (but of course not
> the put call). Read ERR_OR_NULL as appropriate.
> 
> Rasmus
> 
> 

Thanks. Makes sense.  A reference in another thread where this was being discussed
lead me to a reference to Linus arguing for just this:
https://lore.kernel.org/all/20230814161731.GN776869@hirez.programming.kicks-ass.net/

  reply	other threads:[~2024-01-08 12:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-01 17:25 [RFC PATCH 00/13] device property / IIO: Use cleanup.h magic for fwnode_handle_put() handling Jonathan Cameron
2024-01-01 17:25 ` [RFC PATCH 01/13] device property: Add cleanup.h based fwnode_handle_put() scope based cleanup Jonathan Cameron
2024-01-06 15:16   ` Andy Shevchenko
2024-01-06 17:53     ` Jonathan Cameron
2024-01-07 21:05       ` Rasmus Villemoes
2024-01-08 12:51         ` Jonathan Cameron [this message]
2024-01-01 17:26 ` [RFC PATCH 02/13] iio: adc: max11410: Use __free(fwnode_handle) to replace fwnode_handle_put() calls Jonathan Cameron
2024-01-01 17:26 ` [RFC PATCH 03/13] iio: adc: mcp3564: " Jonathan Cameron
2024-01-01 17:26 ` [RFC PATCH 04/13] iio: adc: qcom-spmi-adc5: " Jonathan Cameron
2024-01-01 17:26 ` [RFC PATCH 05/13] iio: adc: rzg2l_adc: " Jonathan Cameron
2024-01-01 17:26 ` [RFC PATCH 06/13] iio: adc: stm32: " Jonathan Cameron
2024-01-01 17:26 ` [RFC PATCH 07/13] iio: adc: ti-ads1015: " Jonathan Cameron
2024-01-01 17:26 ` [RFC PATCH 08/13] iio: adc: ti-ads131e08: " Jonathan Cameron
2024-01-01 17:26 ` [RFC PATCH 09/13] iio: addac: ad74413r: " Jonathan Cameron
2024-01-01 17:26 ` [RFC PATCH 10/13] iio: dac: ad3552: " Jonathan Cameron
2024-01-01 17:26 ` [RFC PATCH 11/13] iio: dac: ad5770r: " Jonathan Cameron
2024-01-01 17:26 ` [RFC PATCH 12/13] iio: dac: ltc2688: " Jonathan Cameron
2024-01-01 17:26 ` [RFC PATCH 13/13] iio: temp: ltc2983: " Jonathan Cameron
2024-01-06 15:19 ` [RFC PATCH 00/13] device property / IIO: Use cleanup.h magic for fwnode_handle_put() handling Andy Shevchenko

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=20240108125117.000010fb@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jic23@jic23.retrosnub.co.uk \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    /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