netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	David Miller <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 5/5] net: phy: remove gen10g_no_soft_reset
Date: Sun, 3 Mar 2019 16:45:03 +0100	[thread overview]
Message-ID: <20190303154503.GD11621@lunn.ch> (raw)
In-Reply-To: <97d4eb8e-3f75-1647-7ca3-26a5ddb5fda0@gmail.com>

On Sat, Mar 02, 2019 at 05:13:11PM +0100, Heiner Kallweit wrote:
> genphy_no_soft_reset and gen10g_no_soft_reset are both the same no-ops,
> one is enough.
> 
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>


Reviewed-by: Andrew Lunn <andrew@lunn.ch>

    Andrew

  reply	other threads:[~2019-03-03 15:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-02 16:09 [PATCH net-next 0/5] net: phy: clean up the old gen10g functions Heiner Kallweit
2019-03-02 16:10 ` [PATCH net-next 1/5] net: phy: use genphy_c45_aneg_done in genphy_aneg_done Heiner Kallweit
2019-03-03 15:34   ` Andrew Lunn
2019-03-02 16:10 ` [PATCH net-next 2/5] net: phy: remove gen10g_suspend and gen10g_resume Heiner Kallweit
2019-03-03 15:37   ` Andrew Lunn
2019-03-02 16:11 ` [PATCH net-next 3/5] net: phy: remove gen10g_config_init Heiner Kallweit
2019-03-03 15:39   ` Andrew Lunn
2019-03-02 16:13 ` [PATCH net-next 5/5] net: phy: remove gen10g_no_soft_reset Heiner Kallweit
2019-03-03 15:45   ` Andrew Lunn [this message]
2019-03-02 16:15 ` [PATCH net-next 4/5] net: phy: don't export gen10g_read_status Heiner Kallweit
2019-03-03 15:48   ` Andrew Lunn
2019-03-03 15:58   ` Andrew Lunn
2019-03-03 16:12     ` Heiner Kallweit
2019-03-04 15:26       ` Jose Abreu
2019-03-04 15:52         ` Andrew Lunn
2019-03-04  5:48 ` [PATCH net-next 0/5] net: phy: clean up the old gen10g functions David Miller

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=20190303154503.GD11621@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@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).