[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200319085812.GA20761@lunn.ch>
Date: Thu, 19 Mar 2020 09:58:12 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Marek Behun <marek.behun@....cz>
Cc: Chris Packham <Chris.Packham@...iedtelesis.co.nz>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next] net: mvmdio: fix driver probe on missing irq
On Thu, Mar 19, 2020 at 05:36:59AM +0100, Marek Behun wrote:
> On Thu, 19 Mar 2020 04:27:56 +0000
> Chris Packham <Chris.Packham@...iedtelesis.co.nz> wrote:
>
> > On Thu, 2020-03-19 at 05:21 +0100, Marek Behun wrote:
> > > On Thu, 19 Mar 2020 02:00:57 +0000
> > > Chris Packham <Chris.Packham@...iedtelesis.co.nz> wrote:
> > >
> > > > Hi Marek,
> > > >
> > > > On Thu, 2020-03-19 at 02:29 +0100, Marek BehĂșn wrote:
> > > > > Commit e1f550dc44a4 made the use of platform_get_irq_optional, which can
> > > > > return -ENXIO when interrupt is missing. Handle this as non-error,
> > > > > otherwise the driver won't probe.
> > > >
> > > > This has already been fixed in net/master by reverting e1f550dc44a4 and
> > > > replacing it with fa2632f74e57bbc869c8ad37751a11b6147a3acc.
> > >
> > > :( It isn't in net-next. I've spent like an hour debugging it :-D
> >
> > I can only offer my humble apologies and promise to do better next
> > time. I did test the first minimally correct change, but clearly
> > stuffed up on v2.
>
> That's ok, but this should be also in net-next as well. Has Dave
> forgotten to apply it there, or is there some other plan?
It probably went into net. It then takes around a week before net is
merged into net-next.
Andrew
Powered by blists - more mailing lists