From: mw@semihalf.com (Marcin Wojtas)
To: linux-arm-kernel@lists.infradead.org
Subject: [net-next: PATCH v2 4/5] net: mvpp2: use device_*/fwnode_* APIs instead of of_*
Date: Mon, 1 Jan 2018 11:04:30 +0100 [thread overview]
Message-ID: <CAPv3WKfiR_ekc-ODPfYWDkP0UG0znRxsTCr6FPePgZVXB5J_zw@mail.gmail.com> (raw)
In-Reply-To: <20171231191836.GA20455@lunn.ch>
Hi Andrew,
2017-12-31 20:18 GMT+01:00 Andrew Lunn <andrew@lunn.ch>:
> On Sun, Dec 31, 2017 at 12:58:39PM +0100, Marcin Wojtas wrote:
> Hi Marcin
>
>> Because there is no equivalent for for_each_available_child_of_node(),
>> use device_for_each_child_node() and check the port availability
>> inside the mvpp2_port_probe() routine.
>
> Could device_each_available_child_node() be added? I guess this will
> not be the last driver converted in this way, and having that macro
> will help with future ports.
>
Sure, I can add it in the next round.
Thanks,
Marcin
next prev parent reply other threads:[~2018-01-01 10:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 11:58 [net-next: PATCH v2 0/5] Armada 7k/8k PP2 ACPI support Marcin Wojtas
2017-12-31 11:58 ` [net-next: PATCH v2 1/5] device property: Introduce fwnode_get_mac_address() Marcin Wojtas
2018-01-03 11:27 ` Rafael J. Wysocki
2017-12-31 11:58 ` [net-next: PATCH v2 2/5] device property: Introduce fwnode_get_phy_mode() Marcin Wojtas
2018-01-03 11:27 ` Rafael J. Wysocki
2017-12-31 11:58 ` [net-next: PATCH v2 3/5] net: mvpp2: simplify maintaining enabled ports' list Marcin Wojtas
2017-12-31 11:58 ` [net-next: PATCH v2 4/5] net: mvpp2: use device_*/fwnode_* APIs instead of of_* Marcin Wojtas
2017-12-31 19:18 ` Andrew Lunn
2018-01-01 10:04 ` Marcin Wojtas [this message]
2017-12-31 11:58 ` [net-next: PATCH v2 5/5] net: mvpp2: enable ACPI support in the driver Marcin Wojtas
2017-12-31 19:23 ` Andrew Lunn
2018-01-01 10:10 ` Marcin Wojtas
2018-01-02 13:33 ` Andrew Lunn
2018-01-02 13:55 ` Marcin Wojtas
2018-01-02 14:08 ` Andrew Lunn
2018-01-02 15:05 ` Marcin Wojtas
2018-01-02 17:22 ` Florian Fainelli
2018-01-03 11:16 ` graeme.gregory at linaro.org
2018-01-03 11:19 ` Marcin Wojtas
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=CAPv3WKfiR_ekc-ODPfYWDkP0UG0znRxsTCr6FPePgZVXB5J_zw@mail.gmail.com \
--to=mw@semihalf.com \
--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).