From: Peter Rosin <peda@axentia.se>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
linux-kernel@vger.kernel.org
Cc: linux-i2c@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH 2/2] i2c: pca9541: Export OF device ID table as module aliases
Date: Sat, 21 Jan 2017 16:56:21 +0100 [thread overview]
Message-ID: <41c2e7eb-5250-d8c6-5803-cab447a2ebd4@axentia.se> (raw)
In-Reply-To: <1484574895-952-2-git-send-email-javier@osg.samsung.com>
On 2017-01-16 14:54, Javier Martinez Canillas wrote:
> The I2C core always reports a MODALIAS of the form i2c:<foo> even if the
> device was registered via OF, this means that exporting the OF device ID
> table device aliases in the module is not needed. But in order to change
> how the core reports modaliases to user-space, it's better to export it.
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
Acked-by: Peter Rosin <peda@axentia.se>
> ---
>
> drivers/i2c/muxes/i2c-mux-pca9541.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/i2c/muxes/i2c-mux-pca9541.c b/drivers/i2c/muxes/i2c-mux-pca9541.c
> index 4ea7e691afc7..77840f7845a1 100644
> --- a/drivers/i2c/muxes/i2c-mux-pca9541.c
> +++ b/drivers/i2c/muxes/i2c-mux-pca9541.c
> @@ -90,6 +90,7 @@ static const struct of_device_id pca9541_of_match[] = {
> { .compatible = "nxp,pca9541" },
> {}
> };
> +MODULE_DEVICE_TABLE(of, pca9541_of_match);
> #endif
>
> /*
>
next prev parent reply other threads:[~2017-01-21 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 13:54 [PATCH 1/2] i2c: mux: pca954x: " Javier Martinez Canillas
2017-01-16 13:54 ` [PATCH 2/2] i2c: pca9541: " Javier Martinez Canillas
2017-01-21 15:56 ` Peter Rosin [this message]
2017-01-21 15:56 ` [PATCH 1/2] i2c: mux: pca954x: " Peter Rosin
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=41c2e7eb-5250-d8c6-5803-cab447a2ebd4@axentia.se \
--to=peda@axentia.se \
--cc=javier@osg.samsung.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wsa@the-dreams.de \
/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
all inboxes | Powered by JetHome®