From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] net/phy: Improvements to Cavium Thunder MDIO code.
Date: Mon, 14 Mar 2016 16:18:51 -0400 (EDT) [thread overview]
Message-ID: <20160314.161851.1859011194305606637.davem@davemloft.net> (raw)
In-Reply-To: <56E71B45.1010805@caviumnetworks.com>
From: David Daney <ddaney@caviumnetworks.com>
Date: Mon, 14 Mar 2016 13:12:53 -0700
> At this point, I think the best path forward is for me to rebase
> against net-next and send you a small fixup set to what was merged.
>
> What do you think?
That is in fact the one and only option.
prev parent reply other threads:[~2016-03-14 20:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 17:53 [PATCH v2 0/3] net/phy: Improvements to Cavium Thunder MDIO code David Daney
2016-03-11 17:53 ` [PATCH v2 1/3] net: thunderx: Cleanup PHY probing code David Daney
2016-03-11 17:53 ` [PATCH v2 2/3] phy: mdio-octeon: Refactor into two files/modules David Daney
2016-03-11 17:53 ` [PATCH v2 3/3] phy: mdio-thunder: Add driver for Cavium Thunder SoC MDIO buses David Daney
2016-03-16 22:50 ` Andreas Färber
2016-03-16 22:54 ` David Daney
2016-03-16 23:24 ` Andreas Färber
2016-03-12 0:08 ` [PATCH v2 0/3] net/phy: Improvements to Cavium Thunder MDIO code David Daney
2016-03-14 19:27 ` David Miller
2016-03-14 20:12 ` David Daney
2016-03-14 20:18 ` 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=20160314.161851.1859011194305606637.davem@davemloft.net \
--to=davem@davemloft.net \
--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).