From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH net-next v3 06/10] net: dsa: Migrate to device_find_class()
Date: Tue, 24 Jan 2017 10:59:15 -0800 [thread overview]
Message-ID: <c98f3ff8-9d4e-a007-1fef-130fcf580201@gmail.com> (raw)
In-Reply-To: <841dc133-e9af-e7ca-75bf-8371337d6281@gmail.com>
On 01/19/2017 10:12 AM, Florian Fainelli wrote:
>
> Back to the actual code that triggered this discussion, the whole
> purpose is just a safeguard. Given a device reference, we can assume
> that it is indeed the backing device for a net_device, and we could do a
> to_net_device() right away (and crash if someone did not write correct
> platform_data structures), or, by walking the device tree (the device
> driver model one) we can make sure it does belong in the proper class
> and this is indeed what we think it is.
Greg, did Russell's explanation clarify things, or do you still think
this is completely bogus and we need to re design the whole thing?
Just asking so I can try to resubmit just the preparatory parts or just
the whole thing.
Thank you
--
Florian
next prev parent reply other threads:[~2017-01-24 18:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 21:47 [PATCH net-next v3 00/10] net: dsa: Support for pdata in dsa2 Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 01/10] net: dsa: Pass device pointer to dsa_register_switch Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 02/10] net: dsa: Make most functions take a dsa_port argument Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 03/10] net: dsa: Suffix function manipulating device_node with _dn Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 04/10] net: dsa: Move ports assignment closer to error checking Florian Fainelli
2017-01-15 10:17 ` Sergei Shtylyov
2017-01-14 21:47 ` [PATCH net-next v3 05/10] drivers: base: Add device_find_class() Florian Fainelli
2017-01-15 11:04 ` Greg KH
2017-01-15 17:39 ` Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 06/10] net: dsa: Migrate to device_find_class() Florian Fainelli
2017-01-15 11:06 ` Greg KH
2017-01-15 17:27 ` Florian Fainelli
2017-01-15 17:39 ` Greg KH
2017-01-15 17:52 ` Florian Fainelli
2017-01-15 19:16 ` Andrew Lunn
2017-01-16 20:01 ` Florian Fainelli
2017-01-18 7:06 ` Greg KH
2017-01-19 14:28 ` Greg KH
2017-01-19 14:53 ` Andrew Lunn
2017-01-19 16:30 ` Greg KH
2017-01-19 16:35 ` Russell King - ARM Linux
2017-01-19 16:51 ` Russell King - ARM Linux
2017-01-19 18:12 ` Florian Fainelli
2017-01-24 18:59 ` Florian Fainelli [this message]
2017-01-25 21:25 ` Greg KH
2017-01-30 22:46 ` Florian Fainelli
2017-02-10 13:02 ` Greg KH
2017-02-10 18:30 ` Florian Fainelli
2017-02-12 12:56 ` Greg KH
2017-01-14 21:47 ` [PATCH net-next v3 07/10] net: Relocate dev_to_net_device() into core Florian Fainelli
2017-01-15 11:07 ` Greg KH
2017-01-15 17:20 ` Florian Fainelli
2017-01-15 17:40 ` Greg KH
2017-01-14 21:47 ` [PATCH net-next v3 08/10] net: dsa: Add support for platform data Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 09/10] net: phy: Allow pre-declaration of MDIO devices Florian Fainelli
2017-01-14 21:47 ` [PATCH net-next v3 10/10] ARM: orion: Register DSA switch as a MDIO device Florian Fainelli
2017-01-15 11:08 ` [PATCH net-next v3 00/10] net: dsa: Support for pdata in dsa2 Greg KH
2017-01-15 17:40 ` Florian Fainelli
2017-01-15 17:49 ` Greg KH
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=c98f3ff8-9d4e-a007-1fef-130fcf580201@gmail.com \
--to=f.fainelli@gmail.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).