All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: David Miller <davem@davemloft.net>
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, 4 Jul 2016 14:40:28 -0700	[thread overview]
Message-ID: <577AD7CC.9010908@gmail.com> (raw)
In-Reply-To: <20160629.061201.2186992042260603628.davem@davemloft.net>

Le 29/06/2016 03:12, David Miller a écrit :
> From: Florian Fainelli <f.fainelli@gmail.com>
> Date: Mon, 27 Jun 2016 18:19:28 -0700
> 
>> 2016-06-27 18:05 GMT-07:00 Andrew Lunn <andrew@lunn.ch>:
>>> On Mon, Jun 27, 2016 at 05:52:37PM -0700, Florian Fainelli wrote:
>>>> Hi all,
>>>>
>>>> This patch series adds support for platform data using the new code from
>>>> net/dsa/dsa2.c. The motivation behind this is that we have a bit of in tree
>>>> platforms (ar7, bcm47xx, x86, others) that could be benefiting from the new
>>>> dsa_register_switch() API model but do not support Device Tree, nor is there a
>>>> plan to bring Device Tree to these platforms (time vs. benefits).
>>>
>>> Hi Florian
>>>
>>> Please could you convert an in tree device to actually use this.
>>
>> Sure, I don't think there are going to be in tree users who need the
>> dsa2_port_link information most of what we have is typically single
>> chip, and so in that case, we can even re-use the existing
>> dsa_platform_data.
> 
> I assume therefore that this series will be resubmitted with an
> accompanying example in-tree conversion.
> 

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).
-- 
Florian

  reply	other threads:[~2016-07-04 21:40 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 [this message]
2016-07-04 22:06         ` 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=577AD7CC.9010908@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.