[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y8e8Nm2lu1jFE6Mx@hovoldconsulting.com>
Date: Wed, 18 Jan 2023 10:30:30 +0100
From: Johan Hovold <johan@...nel.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Johan Hovold <johan+linaro@...nel.org>,
Marc Zyngier <maz@...nel.org>, x86@...nel.org,
platform-driver-x86@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org, Hsin-Yi Wang <hsinyi@...omium.org>,
Mark-PK Tsai <mark-pk.tsai@...iatek.com>
Subject: Re: [PATCH v4 08/19] irqdomain: Refactor __irq_domain_alloc_irqs()
On Tue, Jan 17, 2023 at 10:34:40PM +0100, Thomas Gleixner wrote:
> On Mon, Jan 16 2023 at 14:50, Johan Hovold wrote:
> > -int __irq_domain_alloc_irqs(struct irq_domain *domain, int irq_base,
> > - unsigned int nr_irqs, int node, void *arg,
> > - bool realloc, const struct irq_affinity_desc *affinity)
> > +static int ___irq_domain_alloc_irqs(struct irq_domain *domain, int irq_base,
> > + unsigned int nr_irqs, int node, void *arg,
> > + bool realloc, const struct irq_affinity_desc *affinity)
>
> __ vs. ___ is almost undistinguishable.
>
> irq_domain_alloc_irqs_locked() nicely explains what this is about, no?
Yeah, wasn't too happy about those three underscores either, but with
the exported function unfortunately already having a double underscore
prefix... I'll try switching to a 'locked' suffix instead.
Johan
Powered by blists - more mailing lists