From: Mark Brown <broonie@kernel.org>
To: Sean Wang <sean.wang@mediatek.com>
Cc: matthias.bgg@gmail.com, linux-spi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: mediatek: remove redundant MODULE_ALIAS entries
Date: Thu, 12 Apr 2018 17:13:23 +0100 [thread overview]
Message-ID: <20180412161323.GH9929@sirena.org.uk> (raw)
In-Reply-To: <1522206543.18424.23.camel@mtkswgap22>
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
On Wed, Mar 28, 2018 at 11:09:03AM +0800, Sean Wang wrote:
> On Wed, 2018-03-28 at 10:14 +0800, Mark Brown wrote:
> > On Mon, Mar 26, 2018 at 06:04:18PM +0800, sean.wang@mediatek.com wrote:
> > > From: Sean Wang <sean.wang@mediatek.com>
> > > MODULE_ALIAS exports information to allow the module to be auto-loaded at
> > > boot for the drivers registered using legacy platform registration.
> > > However, currently the driver is always used by DT-only platform,
> > > MODULE_ALIAS is redundant and should be removed properly.
> > There is no meaningful cost to having the alias there, why remove it?
> It's no explicitly improved to the driver, it only takes less bytes
> in .secion modinfo from 644 bytes to 620 bytes in the observation with
> objdump.
OK, that's a *very* small saving though especially given the block sizes
that filesystems tend to use.
> More importantly, it seems the driver should probably refer to another
> qualified driver at the initial development, but MODULE_ALIAS is
> forgetting to be removed to meet real usage for the module autoload.
I can't parse the above, sorry.
> Even I was curious whether people for the driver know the actual purpose
> the macro it's for.
> Removing MODULE_ALIAS is just to correct the driver to where it should
> be.
To me it's the other way around - ideally platform drivers should
remember to set up the MODULE_ALIAS, just as a joining the dots thing to
make sure that things that work when the driver is built in work when
built as a module.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-04-12 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 10:04 [PATCH] spi: mediatek: remove redundant MODULE_ALIAS entries sean.wang
2018-03-28 2:14 ` Mark Brown
2018-03-28 3:09 ` Sean Wang
2018-04-12 16:13 ` Mark Brown [this message]
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=20180412161323.GH9929@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@mediatek.com \
/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).