[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZN3mraFtdDhDM6Sy@smile.fi.intel.com>
Date: Thu, 17 Aug 2023 12:21:49 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
Kent Gibson <warthog618@...il.com>, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [PATCH 2/2] gpio: sim: simplify code with cleanup helpers
On Wed, Aug 16, 2023 at 02:47:57PM +0200, Peter Zijlstra wrote:
> On Tue, Aug 15, 2023 at 10:31:17PM +0200, Peter Zijlstra wrote:
>
> > > Moreover, maybe some macro that can predict the API call from the type of
> > > the parameter?
> >
> > The whole type inferrence in C is not extensible. That is, you get to
> > write a single _Generic() statement, and every case that is included in
> > it will work, but the moment you use a new type, one that is not
> > included in your giant _Generic() statement, you're out of luck.
>
> Additionally, spinlock_t, does that map to spinlock, spinlock_irq or
> spinlock_irqsave ?
Thank you for a good explanation.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists