From: davem@davemloft.net (David Miller)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 RESEND 0/7] Add MDIO bus multiplexer support for iProc SoCs
Date: Sun, 05 Jun 2016 23:21:35 -0400 (EDT) [thread overview]
Message-ID: <20160605.232135.1270822980912550134.davem@davemloft.net> (raw)
In-Reply-To: <20160603163247.GI22120@lunn.ch>
From: Andrew Lunn <andrew@lunn.ch>
Date: Fri, 3 Jun 2016 18:32:47 +0200
>> Reason for resend:
>> -Rebased on v4.7-rc1
>
> How do you see this getting merged? Via netdev? If so, you should be
> based on net-next/master, not v4.7-rc1.
Indeed, please respin.
Also, in your Subject lines, always have a space after the ":"
characters.
prev parent reply other threads:[~2016-06-06 3:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 16:02 [PATCH v3 RESEND 0/7] Add MDIO bus multiplexer support for iProc SoCs Pramod Kumar
2016-06-03 16:03 ` [PATCH v3 RESEND 1/7] mdio:mux: Enhanced MDIO mux framework for integrated multiplexers Pramod Kumar
2016-06-03 16:03 ` [PATCH v3 RESEND 2/7] binding: Make "mdio-parent-bus" property from mandatory to optional Pramod Kumar
2016-06-03 16:03 ` [PATCH v3 RESEND 3/7] binding: mdio-mux: Add DT binding doc for Broadcom MDIO bus mutiplexer Pramod Kumar
2016-06-03 16:03 ` [PATCH v3 RESEND 4/7] dt:mdio-mux: Add mdio multiplexer driver node Pramod Kumar
2016-06-03 16:03 ` [PATCH v3 RESEND 5/7] net:mdio-mux: Add MDIO mux driver for iProc SoCs Pramod Kumar
2016-06-03 16:03 ` [PATCH v3 RESEND 6/7] Binding:PHY: Binding doc for NS2 PCIe PHYs Pramod Kumar
2016-06-03 16:03 ` [PATCH v3 RESEND 7/7] phy: Add Northstar2 PCI Phy support Pramod Kumar
2016-06-03 16:32 ` [PATCH v3 RESEND 0/7] Add MDIO bus multiplexer support for iProc SoCs Andrew Lunn
2016-06-06 3:21 ` David Miller [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=20160605.232135.1270822980912550134.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.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).