From: Andrew Lunn <andrew@lunn.ch>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: David Miller <davem@davemloft.net>,
f.fainelli@gmail.com, jon@solid-run.com, netdev@vger.kernel.org
Subject: Re: [PATCH] net: phy: marvell: avoid pause mode on SGMII-to-Copper for 88e151x
Date: Fri, 15 Dec 2017 16:48:51 +0100 [thread overview]
Message-ID: <20171215154851.GB17702@lunn.ch> (raw)
In-Reply-To: <20171215154540.GT10595@n2100.armlinux.org.uk>
> Sorry about that, not quite sure how that happened, but here's a
> replacement patch. I assume patchwork will do the right thing by
> including the patch in this mail...
Hi Russell
No, it does not. You need to submit a whole new patch.
Andrew
next prev parent reply other threads:[~2017-12-15 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 9:22 [PATCH] net: phy: marvell: avoid pause mode on SGMII-to-Copper for 88e151x Russell King
2017-12-13 16:44 ` Andrew Lunn
2017-12-13 21:14 ` David Miller
2017-12-15 15:45 ` Russell King - ARM Linux
2017-12-15 15:48 ` Andrew Lunn [this message]
2017-12-15 16:15 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2017-12-15 16:10 Russell King
2017-12-18 20:04 ` 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=20171215154851.GB17702@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jon@solid-run.com \
--cc=linux@armlinux.org.uk \
--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).