[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1908030942180.4029@nanos.tec.linutronix.de>
Date: Sat, 3 Aug 2019 09:43:01 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
cc: Michael Kelley <mikelley@...rosoft.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"boqun.feng" <boqun.feng@...il.com>,
kimbrownkd <kimbrownkd@...il.com>
Subject: Re: [PATCH 1/1] genirq: Properly pair kobject_del with kobject_add
On Sat, 3 Aug 2019, gregkh@...uxfoundation.org wrote:
> On Fri, Aug 02, 2019 at 08:19:37PM +0000, Michael Kelley wrote:
> > > Relying on irq_kobj_base to be present or not seems like an odd test
> > > here.
> > >
> >
> > It's the same test that is used in irq_sysfs_add to decide whether to
> > call kobject_add. So it makes everything paired up and symmetrical.
>
> Ugh, that's a tangled mess and totally not obvious at all. I'm sure
> there's a good reason for all of that, and I really don't want to know
> :)
It's all your fault that the sysfs stuff does not work in very early boot.
/me runs
Powered by blists - more mailing lists