netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Mason <slash.tmp@free.fr>,
	netdev@vger.kernel.org, Daniel Mack <daniel@zonque.org>,
	Fabio Estevam <festevam@gmail.com>,
	Mans Rullgard <mans@mansr.com>
Subject: Re: Small improvements for the at803x PHY driver
Date: Fri, 15 Jan 2016 01:57:14 +0100	[thread overview]
Message-ID: <CAFBinCCsmuLDMBj+KOb1MhFBdeaPeaqzj2J+16E3M2ZBFu4CGA@mail.gmail.com> (raw)
In-Reply-To: <567F5B2E.9050705@gmail.com>

On Sun, Dec 27, 2015 at 4:29 AM, Florian Fainelli <f.fainelli@gmail.com> wrote:
> Overall, this looks pretty nice to me, few comments in individual patches.
I have just sent refreshed versions of all patches and fixed the parts
we've discussed (see the comment section in the corresponding
patches).


Martin

      reply	other threads:[~2016-01-15  0:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-26  0:26 Small improvements for the at803x PHY driver Martin Blumenstingl
2015-12-26  0:26 ` [PATCH 1/4] net: phy: at803x: Don't set gbit features for the AR8030 phy Martin Blumenstingl
2015-12-27  3:24   ` Florian Fainelli
2015-12-26  0:27 ` [PATCH 2/4] net: phy: at803x: Allow specifying the RGMII RX clock delay via phy mode Martin Blumenstingl
2015-12-27  3:28   ` Florian Fainelli
2015-12-27 15:15     ` Martin Blumenstingl
2015-12-27 20:22     ` Mason
2016-01-04 21:17       ` Martin Blumenstingl
2016-01-04 22:05         ` Florian Fainelli
2015-12-26  0:27 ` [PATCH 3/4] net: phy: at803x: Clean up duplicate register definitions Martin Blumenstingl
2015-12-27  3:28   ` Florian Fainelli
2015-12-26  0:27 ` [PATCH 4/4] net: phy: at803x: Add the interrupt register bit definitions Martin Blumenstingl
2015-12-27  3:29   ` Florian Fainelli
2015-12-26 11:57 ` Small improvements for the at803x PHY driver Mason
2015-12-27  3:29   ` Florian Fainelli
2016-01-15  0:57     ` Martin Blumenstingl [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=CAFBinCCsmuLDMBj+KOb1MhFBdeaPeaqzj2J+16E3M2ZBFu4CGA@mail.gmail.com \
    --to=martin.blumenstingl@googlemail.com \
    --cc=daniel@zonque.org \
    --cc=f.fainelli@gmail.com \
    --cc=festevam@gmail.com \
    --cc=mans@mansr.com \
    --cc=netdev@vger.kernel.org \
    --cc=slash.tmp@free.fr \
    /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).