[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a81a46ef13273aa8c6ea87c8d3550e33650e27b6.camel@kernel.crashing.org>
Date: Thu, 06 Jun 2019 07:55:43 +1000
From: Benjamin Herrenschmidt <benh@...nel.crashing.org>
To: Greg KH <gregkh@...uxfoundation.org>,
Talel Shenhar <talel@...zon.com>
Cc: nicolas.ferre@...rochip.com, jason@...edaemon.net,
marc.zyngier@....com, mark.rutland@....com,
mchehab+samsung@...nel.org, robh+dt@...nel.org,
davem@...emloft.net, shawn.lin@...k-chips.com, tglx@...utronix.de,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
dwmw@...zon.co.uk, jonnyc@...zon.com, hhhawa@...zon.com,
ronenk@...zon.com, hanochu@...zon.com, barakw@...zon.com
Subject: Re: [PATCH 2/3] irqchip: al-fic: Introduce Amazon's Annapurna Labs
Fabric Interrupt Controller Driver
On Wed, 2019-06-05 at 09:59 +0200, Greg KH wrote:
>
> > +struct irq_domain *al_fic_wire_get_domain(struct al_fic *fic);
> > +
> > +struct al_fic *al_fic_wire_init(struct device_node *node,
> > + void __iomem *base,
> > + const char *name,
> > + unsigned int parent_irq);
> > +int al_fic_cleanup(struct al_fic *fic);
>
> Who is using these new functions? We don't add new apis that no one
> uses :(
They will be used by subsequent driver submissions but those aren't
quite ready yet, so we can hold onto patch 3 for now until they are.
Cheers,
Ben.
Powered by blists - more mailing lists