On Wed, 20 Feb 2019 16:00:15 +0100
Thomas Bogendoerfer wrote:
> On Wed, 20 Feb 2019 09:15:37 +
> Marc Zyngier wrote:
>
> > Well, short of doing the above, I'd rather have something in the common
> > code that allows the default domain to be retrieved. How about the
> > patch below?
>
>
On Wed, 20 Feb 2019 09:15:37 +
Marc Zyngier wrote:
> Well, short of doing the above, I'd rather have something in the common
> code that allows the default domain to be retrieved. How about the
> patch below?
Works for me:-) Thank you.
Are you going to submit it for v5.1 ?
Thomas.
--
On Tue, 19 Feb 2019 17:48:29 +0100
Thomas Bogendoerfer wrote:
> On Tue, 19 Feb 2019 16:27:16 +
> Marc Zyngier wrote:
>
> > On Tue, 19 Feb 2019 16:57:23 +0100
> > Thomas Bogendoerfer wrote:
> >
> > Hi Thomas,
> >
> > > When creating hierarchy domains use irq_default_domain as parent,
On Tue, 19 Feb 2019 16:27:16 +
Marc Zyngier wrote:
> On Tue, 19 Feb 2019 16:57:23 +0100
> Thomas Bogendoerfer wrote:
>
> Hi Thomas,
>
> > When creating hierarchy domains use irq_default_domain as parent, if no
> > parent was given by the caller. This avoids adding helper code for
> >
On Tue, 19 Feb 2019 16:57:23 +0100
Thomas Bogendoerfer wrote:
Hi Thomas,
> When creating hierarchy domains use irq_default_domain as parent, if no
> parent was given by the caller. This avoids adding helper code for
> querying the underlying platform irq domain.
>
> Signed-off-by: Thomas
When creating hierarchy domains use irq_default_domain as parent, if no
parent was given by the caller. This avoids adding helper code for
querying the underlying platform irq domain.
Signed-off-by: Thomas Bogendoerfer
---
kernel/irq/irqdomain.c | 5 -
1 file changed, 4 insertions(+), 1
6 matches
Mail list logo