linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andres Galacho <andresgalacho@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: broonie@kernel.org, f.fainelli@gmail.com,
	bcm-kernel-feedback-list@broadcom.com, linux-spi@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Andres Galacho <andresgalacho@gmail.com>
Subject: [RESEND PATCH] spi: bcm63xx-hsspi: Export OF device ID table as module aliases
Date: Mon,  1 May 2017 16:13:38 -0400	[thread overview]
Message-ID: <20170501201338.5368-1-andresgalacho@gmail.com> (raw)

The device table is required to load modules based on
modaliases. After adding MODULE_DEVICE_TABLE, below entries
for example will be added to module.alias:
alias:          of:N*T*Cbrcm,bcm6328-hsspiC*
alias:          of:N*T*Cbrcm,bcm6328-hsspi

Signed-off-by: Andres Galacho <andresgalacho@gmail.com>
---
 Resending patch since I forgot to add the lists as cc,
 sorry about the noise.

 drivers/spi/spi-bcm63xx-hsspi.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/spi/spi-bcm63xx-hsspi.c b/drivers/spi/spi-bcm63xx-hsspi.c
index 5514cd02e93a..4da2d4a524ca 100644
--- a/drivers/spi/spi-bcm63xx-hsspi.c
+++ b/drivers/spi/spi-bcm63xx-hsspi.c
@@ -484,6 +484,7 @@ static const struct of_device_id bcm63xx_hsspi_of_match[] = {
 	{ .compatible = "brcm,bcm6328-hsspi", },
 	{ },
 };
+MODULE_DEVICE_TABLE(of, bcm63xx_hsspi_of_match);
 
 static struct platform_driver bcm63xx_hsspi_driver = {
 	.driver = {
-- 
2.11.0

             reply	other threads:[~2017-05-01 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01 20:13 Andres Galacho [this message]
2017-05-02 14:00 ` [RESEND PATCH] spi: bcm63xx-hsspi: Export OF device ID table as module aliases Jonas Gorski
2017-05-05 21:07 ` Florian Fainelli
2017-05-15  8:04 ` Applied "spi: bcm63xx-hsspi: Export OF device ID table as module aliases" to the spi tree Mark Brown

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=20170501201338.5368-1-andresgalacho@gmail.com \
    --to=andresgalacho@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=broonie@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@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).