From: Paul Bolle <pebolle@tiscali.nl>
To: Matt Porter <mporter@konsulko.com>
Cc: Linux IIO List <linux-iio@vger.kernel.org>,
Devicetree List <devicetree@vger.kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] iio: temperature: add max6675 thermocouple converter driver
Date: Tue, 04 Aug 2015 11:30:36 +0200 [thread overview]
Message-ID: <1438680636.8734.45.camel@tiscali.nl> (raw)
In-Reply-To: <1438635410-3757-3-git-send-email-mporter@konsulko.com>
On ma, 2015-08-03 at 16:56 -0400, Matt Porter wrote:
> --- /dev/null
> +++ b/drivers/iio/temperature/max6675.c
> +static const struct spi_device_id max6675_spi_ids[] = {
> + {"max6675", 0},
> + {},
> +};
> +MODULE_DEVICE_TABLE(spi, max6675_spi_ids);
> +MODULE_ALIAS("spi:max6675");
For the "spi" alias this is "belt and suspenders":
modinfo ./max6675.ko | grep alias
alias: spi:max6675
alias: acpi*:MXIM6675:*
alias: of:N*T*Cmaxim,max6675*
alias: spi:max6675
I'd drop the MODULE_ALIAS().
(Mark Brown made it quite clear I shouldn't nag people about the origin
of the various strings used in these module aliases. So I won't. But if
you'd volunteer to explain me where "max6675" might come from for the
spi alias that would, at least, satisfy my curiosity.)
Thanks,
Paul Bolle
next prev parent reply other threads:[~2015-08-04 9:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 20:56 [PATCH 0/3] MAX6675 IIO temperature driver Matt Porter
2015-08-03 20:56 ` [PATCH 1/3] iio: temperature: add max6675 dt binding Matt Porter
2015-08-03 20:56 ` [PATCH 2/3] iio: temperature: add max6675 thermocouple converter driver Matt Porter
2015-08-03 21:26 ` Peter Meerwald
2015-08-03 23:13 ` Matt Porter
2015-08-06 17:38 ` Matt Porter
2015-08-08 11:39 ` Jonathan Cameron
2015-08-20 0:23 ` Matt Porter
2015-08-23 15:44 ` Jonathan Cameron
2015-08-03 22:39 ` Matt Ranostay
2015-08-03 23:10 ` Matt Porter
2015-08-04 7:50 ` Daniel Baluta
2015-08-04 13:01 ` Matt Porter
2015-08-04 9:30 ` Paul Bolle [this message]
2015-08-04 13:18 ` Matt Porter
2015-08-03 20:56 ` [PATCH 3/3] MAINTAINERS: add max6675 driver Matt Porter
2015-08-04 16:52 ` [PATCH 0/3] MAX6675 IIO temperature driver Jonathan Cameron
2015-08-04 17:34 ` Matt Porter
2015-08-05 8:33 ` Daniel Baluta
2015-08-05 11:43 ` Matt Porter
2015-08-08 11:36 ` Jonathan Cameron
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=1438680636.8734.45.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mporter@konsulko.com \
--cc=robh+dt@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