From: David Miller <davem@davemloft.net>
To: quentin.schulz@bootlin.com
Cc: alexandre.belloni@bootlin.com, ralf@linux-mips.org,
paul.burton@mips.com, jhogan@kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, andrew@lunn.ch, f.fainelli@gmail.com,
allan.nielsen@microchip.com, linux-mips@linux-mips.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, thomas.petazzoni@bootlin.com,
antoine.tenart@bootlin.com
Subject: Re: [PATCH v2 0/5] net: phy: mscc: add support for VSC8584 and VSC8574 Microsemi quad-port PHYs
Date: Fri, 05 Oct 2018 14:42:43 -0700 (PDT) [thread overview]
Message-ID: <20181005.144243.1971242720262167660.davem@davemloft.net> (raw)
In-Reply-To: <20181004131710.14978-1-quentin.schulz@bootlin.com>
From: Quentin Schulz <quentin.schulz@bootlin.com>
Date: Thu, 4 Oct 2018 15:17:05 +0200
> I suggest patches 1 to 3 go through net tree and patches 4 and 5 go
> through MIPS tree. Patches going through net tree and those going through
> MIPS tree do not depend on one another.
Sounds like a good plan but patches 1-3 do not apply to net-next, please
respin.
Thank you.
next prev parent reply other threads:[~2018-10-05 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 13:17 [PATCH v2 0/5] net: phy: mscc: add support for VSC8584 and VSC8574 Microsemi quad-port PHYs Quentin Schulz
2018-10-04 13:17 ` [PATCH net-next v2 1/5] dt-bindings: net: vsc8531: add two additional LED modes for VSC8584 Quentin Schulz
2018-10-04 13:17 ` [PATCH net-next v2 2/5] net: phy: mscc: add support for VSC8584 PHY Quentin Schulz
2018-10-04 13:17 ` [PATCH v2 net-next 3/5] net: phy: mscc: add support for VSC8574 PHY Quentin Schulz
2018-10-04 13:17 ` [PATCH v2 4/5] MIPS: mscc: add DT for Ocelot PCB120 Quentin Schulz
2018-10-04 13:17 ` [PATCH v2 5/5] MIPS: mscc: add PCB120 to the ocelot fitImage Quentin Schulz
2018-10-05 21:42 ` David Miller [this message]
2018-10-08 7:06 ` [PATCH v2 0/5] net: phy: mscc: add support for VSC8584 and VSC8574 Microsemi quad-port PHYs Quentin Schulz
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=20181005.144243.1971242720262167660.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexandre.belloni@bootlin.com \
--cc=allan.nielsen@microchip.com \
--cc=andrew@lunn.ch \
--cc=antoine.tenart@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jhogan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=quentin.schulz@bootlin.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
/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).