From: Andrew Lunn <andrew@lunn.ch>
To: Dan Murphy <dmurphy@ti.com>
Cc: f.fainelli@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] net: phy: DP83TC811: Add INT_STAT3
Date: Thu, 28 Jun 2018 14:04:53 +0200 [thread overview]
Message-ID: <20180628120453.GA23295@lunn.ch> (raw)
In-Reply-To: <98e615dd-3fa7-78b2-3401-13cae4916c14@ti.com>
> Yes I was debating whether to include this change in the patch or have it
> stand alone for stable back port.
>
> I will pull it out and cc stable
No need to CC stable. Base the patch on daveM net branch, and David
will do the rest.
You probably want to wait a week or two before sending the other
patches for net-next. You want net to be merged into net-next, in
order to avoid conflicts.
Andrew
prev parent reply other threads:[~2018-06-28 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 18:16 [PATCH 1/2] net: phy: DP83TC811: Add INT_STAT3 Dan Murphy
2018-06-27 18:16 ` [PATCH 2/2] net: phy: DP83TC811: Fix SGMII enable/disable Dan Murphy
2018-06-28 8:20 ` Andrew Lunn
2018-06-28 11:53 ` Dan Murphy
2018-06-28 8:16 ` [PATCH 1/2] net: phy: DP83TC811: Add INT_STAT3 Andrew Lunn
2018-06-28 11:54 ` Dan Murphy
2018-06-28 12:04 ` Andrew Lunn [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=20180628120453.GA23295@lunn.ch \
--to=andrew@lunn.ch \
--cc=dmurphy@ti.com \
--cc=f.fainelli@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).