From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <gabriel.fernandez@linaro.org>,
<afaerber@suse.de>, <fschaefer.oss@googlemail.com>,
<dinh.linux@gmail.com>, <preid@electromag.com.au>
Subject: Re: [PATCH (net-next.git) 0/2] STMMAC: MDIO settings
Date: Thu, 17 Mar 2016 14:10:17 +0100 [thread overview]
Message-ID: <56EAACB9.40803@st.com> (raw)
In-Reply-To: <20160316.180905.1210684680763742658.davem@davemloft.net>
On 3/16/2016 11:09 PM, David Miller wrote:
>
> Don't _ever_ send the same two sets of patches targetting net and
> net-next at the same time.
cover-letter reports the difference between the two patches for
net and next.
> Especially right now, as 'net' is basically frozen, and 'net-next' is
> closed for new features and is only for last minute bug fixes before I
> send a merge window pull request to Linus.
I do think that:
[PATCH (net-next.git) 0/2] STMMAC: MDIO settings
[PATCH (net-next.git)] stmmac: fix TX normal DESC
are last minute bug fixes for net-next.
Peppe
>
> I'm tossing both of these series, figure it how to do this properly.
next prev parent reply other threads:[~2016-03-17 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 9:52 [PATCH (net-next.git) 0/2] STMMAC: MDIO settings Giuseppe Cavallaro
2016-03-16 9:52 ` [PATCH (net-next.git) 1/2] Revert "stmmac: Fix 'eth0: No PHY found' regression" Giuseppe Cavallaro
2016-03-16 9:52 ` [PATCH (net-next.git) 2/2] stmmac: fix MDIO settings Giuseppe Cavallaro
2016-03-16 11:01 ` Gabriel Fernandez
2016-03-16 11:03 ` Andreas Färber
2016-03-16 12:53 ` Giuseppe CAVALLARO
2016-03-16 10:47 ` [PATCH (net-next.git) 0/2] STMMAC: " Andreas Färber
2016-03-16 22:09 ` David Miller
2016-03-17 13:10 ` Giuseppe CAVALLARO [this message]
2016-03-18 1:12 ` 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=56EAACB9.40803@st.com \
--to=peppe.cavallaro@st.com \
--cc=afaerber@suse.de \
--cc=davem@davemloft.net \
--cc=dinh.linux@gmail.com \
--cc=fschaefer.oss@googlemail.com \
--cc=gabriel.fernandez@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=preid@electromag.com.au \
/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).