From: David Miller <davem@davemloft.net>
To: andrew@lunn.ch
Cc: f.fainelli@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] Fix breakage from mdio device
Date: Sun, 10 Jan 2016 18:04:00 -0500 (EST) [thread overview]
Message-ID: <20160110.180400.1308724777481360115.davem@davemloft.net> (raw)
In-Reply-To: <1452200152-15793-1-git-send-email-andrew@lunn.ch>
From: Andrew Lunn <andrew@lunn.ch>
Date: Thu, 7 Jan 2016 21:55:50 +0100
> These two patches fix MIPS platforms which got broken by
> the recent mdio device patchset.
Series applied, thanks Andrew.
prev parent reply other threads:[~2016-01-10 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 20:55 [PATCH net-next 0/2] Fix breakage from mdio device Andrew Lunn
2016-01-07 20:55 ` [PATCH net-next 1/2] net: lantiq_etop.c: Use helper to find first phy Andrew Lunn
2016-01-07 20:55 ` [PATCH net-next 2/2] net: ethernet-rgmii.c: Fix breakage from moving phdev bus Andrew Lunn
2016-01-10 23:04 ` David Miller [this message]
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=20160110.180400.1308724777481360115.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.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).