From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/8] arm64: rockchip: Initial GeekBox enablement
Date: Mon, 07 Mar 2016 13:24:25 +0100 [thread overview]
Message-ID: <2714888.1DdqvJZ8cb@diego> (raw)
In-Reply-To: <56DD7172.4000707@suse.de>
Hi Andreas,
Am Montag, 7. M?rz 2016, 13:17:54 schrieb Andreas F?rber:
> Am 06.03.2016 um 20:53 schrieb Andreas F?rber:
> > On next-20160304 the GMAC seems to have regressed, it no longer finds the
> > PHY:
> >
> > libphy: PHY stmmac-0:ffffffff not found
> > eth0: Could not attach to PHY
> > stmmac_open: Cannot attach to PHY (error: -19)
>
> Still with us in next-20160307. CC'ing stmmac maintainers.
do you remember from what revision you rebased away from, when it was still
working (as a known-good state)?
Heiko
>
> http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/drivers/
> net/ethernet/stmicro
>
> Regards,
> Andreas
next prev parent reply other threads:[~2016-03-07 12:24 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1457294038-14243-1-git-send-email-afaerber@suse.de>
2016-03-06 19:53 ` [PATCH v3 2/8] Documentation: devicetree: rockchip: Document GeekBox Andreas Färber
2016-03-06 19:53 ` [PATCH v3 3/8] arm64: dts: rockchip: Add GeekBox config Andreas Färber
2016-03-06 19:53 ` [PATCH v3 5/8] arm64: dts: rockchip: Clean up gpio-keys nodes Andreas Färber
2016-03-06 19:53 ` [PATCH v3 6/8] arm64: dts: rockchip: Add power key to GeekBox Andreas Färber
2016-03-10 23:04 ` Julien Chauveau
2016-03-16 10:58 ` Andreas Färber
2016-03-16 13:52 ` Andreas Färber
2016-03-10 23:09 ` Julien Chauveau
2016-03-06 19:53 ` [PATCH v3 7/8] Documentation: devicetree: rockchip: Document Landingship Andreas Färber
2016-03-17 14:46 ` Rob Herring
2016-03-06 19:53 ` [PATCH v3 8/8] arm64: dts: rockchip: Add Landingship config Andreas Färber
2016-03-07 12:17 ` [PATCH v3 0/8] arm64: rockchip: Initial GeekBox enablement Andreas Färber
2016-03-07 12:24 ` Heiko Stübner [this message]
2016-03-07 12:35 ` Andreas Färber
2016-03-07 13:26 ` Giuseppe CAVALLARO
2016-03-07 14:27 ` Andreas Färber
2016-03-07 15:09 ` Giuseppe CAVALLARO
2016-03-07 15:46 ` Andreas Färber
2016-03-07 15:52 ` Giuseppe CAVALLARO
2016-03-07 17:15 ` Andreas Färber
2016-03-07 23:22 ` Dinh Nguyen
2016-03-08 7:24 ` Giuseppe CAVALLARO
2016-03-08 15:45 ` Dinh Nguyen
2016-03-09 7:24 ` Giuseppe CAVALLARO
2016-03-09 8:35 ` Tomeu Vizoso
2016-03-09 8:56 ` Giuseppe CAVALLARO
2016-03-09 9:00 ` Giuseppe CAVALLARO
2016-03-09 9:42 ` Tomeu Vizoso
2016-03-09 9:52 ` Giuseppe CAVALLARO
2016-03-09 10:27 ` Giuseppe CAVALLARO
2016-03-09 10:53 ` Tomeu Vizoso
2016-03-09 14:31 ` Giuseppe CAVALLARO
2016-03-09 14:53 ` Giuseppe CAVALLARO
2016-03-09 16:31 ` Dinh Nguyen
2016-03-10 9:13 ` Giuseppe CAVALLARO
2016-03-10 16:47 ` Dinh Nguyen
2016-03-11 9:09 ` Giuseppe CAVALLARO
2016-03-14 11:43 ` Tomeu Vizoso
2016-03-14 16:20 ` Giuseppe CAVALLARO
2016-03-15 7:23 ` Tomeu Vizoso
2016-03-15 12:36 ` Giuseppe CAVALLARO
2016-03-30 16:44 ` Dinh Nguyen
2016-03-31 7:53 ` Giuseppe CAVALLARO
2016-03-08 10:03 ` Gabriel Fernandez
2016-03-08 10:24 ` Giuseppe CAVALLARO
2016-03-08 10:33 ` Gabriel Fernandez
2016-03-11 12:12 ` Michael Trimarchi
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=2714888.1DdqvJZ8cb@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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).