From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: andrew@lunn.ch, netdev@vger.kernel.org,
vivien.didelot@savoirfairelinux.com
Subject: Re: [PATCH net-next 0/6] net: dsa: Platform data for dsa2.c
Date: Mon, 04 Jul 2016 15:06:16 -0700 (PDT) [thread overview]
Message-ID: <20160704.150616.1725846601292911147.davem@davemloft.net> (raw)
In-Reply-To: <577AD7CC.9010908@gmail.com>
From: Florian Fainelli <f.fainelli@gmail.com>
Date: Mon, 4 Jul 2016 14:40:28 -0700
> That is correct, although patches 1-4 could be applied immediately as
> they are mostly preparatory steps to patches 5-6, I don't mind resending
> this at a later time though (probably for the next net-next merge window
> I assume).
Depends upon how quickly you do the work and resubmit.
prev parent reply other threads:[~2016-07-04 22:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 0:52 [PATCH net-next 0/6] net: dsa: Platform data for dsa2.c Florian Fainelli
2016-06-28 0:52 ` [PATCH net-next 1/6] net: dsa: Pass device pointer to dsa_register_switch Florian Fainelli
2016-06-28 0:52 ` [PATCH net-next 2/6] net: dsa: Make most functions take a dsa_port argument Florian Fainelli
2016-06-28 0:52 ` [PATCH net-next 3/6] net: dsa: Suffix function manipulating device_node with _dn Florian Fainelli
2016-06-28 0:52 ` [PATCH net-next 4/6] net: dsa: Move ports assignment closer to error checking Florian Fainelli
2016-06-28 0:52 ` [PATCH net-next 5/6] net: dsa: Export dev_to_net_device() Florian Fainelli
2016-06-28 0:52 ` [PATCH net-next 6/6] net: dsa: Add support for platform data Florian Fainelli
2016-06-28 1:05 ` [PATCH net-next 0/6] net: dsa: Platform data for dsa2.c Andrew Lunn
2016-06-28 1:19 ` Florian Fainelli
2016-06-28 14:17 ` Andrew Lunn
2016-06-29 10:12 ` David Miller
2016-07-04 21:40 ` Florian Fainelli
2016-07-04 22:06 ` 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=20160704.150616.1725846601292911147.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).