From: Michael Ellerman <mpe@ellerman.id.au>
To: David Miller <davem@davemloft.net>, paul.gortmaker@windriver.com
Cc: benh@kernel.crashing.org, paulus@samba.org,
netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
andrew@lunn.ch
Subject: Re: [PATCH] sbc8641: drop bogus PHY IRQ entries from DTS file
Date: Wed, 09 Dec 2015 14:00:03 +1100 [thread overview]
Message-ID: <1449630003.6028.14.camel@ellerman.id.au> (raw)
In-Reply-To: <20151208.214055.912759732176162258.davem@davemloft.net>
On Tue, 2015-12-08 at 21:40 -0500, David Miller wrote:
> From: Paul Gortmaker <paul.gortmaker@windriver.com>
> Date: Tue, 8 Dec 2015 17:44:02 -0500
> > This file was originally cloned off of the MPC8641D-HPCN reference
> > platform, which actually had a PHY IRQ line connected. However
> > this board does not. The bogus entry was largely inert and went
> > undetected until commit 321beec5047af83db90c88114b7e664b156f49fe
> > ("net: phy: Use interrupts when available in NOLINK state") was
> > added to the tree.
> >
> > With the above commit, the board fails to NFS boot since it sits
> > waiting for a PHY IRQ event that of course never arrives. Removing
> > the bogus entries from the DTS file fixes the issue.
> >
> > Cc: Andrew Lunn <andrew@lunn.ch>
> > Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
>
> I'm assuming this will go via the powerpc tree, not mine.
Yep I'll take it.
cheers
next prev parent reply other threads:[~2015-12-09 3:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 22:44 [PATCH] sbc8641: drop bogus PHY IRQ entries from DTS file Paul Gortmaker
2015-12-09 1:10 ` Michael Ellerman
2015-12-09 2:04 ` Paul Gortmaker
2015-12-09 3:04 ` Michael Ellerman
2015-12-09 2:40 ` David Miller
2015-12-09 3:00 ` Michael Ellerman [this message]
2015-12-09 3:07 ` Andrew Lunn
2015-12-09 14:39 ` Paul Gortmaker
2015-12-09 15:29 ` Andrew Lunn
2015-12-14 9:46 ` Michael Ellerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1449630003.6028.14.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=andrew@lunn.ch \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).