From: Paul Bolle <pebolle@tiscali.nl>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org,
"Aleksey S. Kazantsev" <ioctl@yandex.ru>
Subject: Re: [PATCH] dsa: mv88e6352/mv88e6xxx: Add support for Marvell 88E6320 and 88E6321
Date: Thu, 09 Jul 2015 10:53:23 +0200 [thread overview]
Message-ID: <1436432003.20619.102.camel@tiscali.nl> (raw)
In-Reply-To: <1436326695-18666-1-git-send-email-linux@roeck-us.net>
On di, 2015-07-07 at 20:38 -0700, Guenter Roeck wrote:
> --- a/drivers/net/dsa/mv88e6352.c
> +++ b/drivers/net/dsa/mv88e6352.c
> -MODULE_ALIAS("platform:mv88e6352");
> MODULE_ALIAS("platform:mv88e6172");
> +MODULE_ALIAS("platform:mv88e6176");
> +MODULE_ALIAS("platform:mv88e6320");
> +MODULE_ALIAS("platform:mv88e6321");
> +MODULE_ALIAS("platform:mv88e6352");
Naive question: there are quite a few similar MODULE_ALIAS() macros in
drivers/net/dsa. That is, macros using "platform:mv88e6[...]". But I
couldn't find the struct platform_device's that would, in short, fire
off the corresponding "MODALIAS=platform:mv88e6[...]" uevent when
they're created. Where should I look for those struct platform_device's?
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-07-09 8:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 3:38 [PATCH] dsa: mv88e6352/mv88e6xxx: Add support for Marvell 88E6320 and 88E6321 Guenter Roeck
2015-07-08 14:52 ` Andrew Lunn
2015-07-08 15:08 ` Guenter Roeck
2015-07-09 21:37 ` David Miller
2015-07-09 8:53 ` Paul Bolle [this message]
2015-07-09 18:26 ` Guenter Roeck
2015-07-09 21:37 ` 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=1436432003.20619.102.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=ioctl@yandex.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.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).