From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>
Subject: Re: [PATCH 2/2] regulator: lochnagar: Remove redundant MODULE_ALIAS
Date: Mon, 21 Jan 2019 09:21:55 +0000 [thread overview]
Message-ID: <20190121092155.GG3837@imbe.wolfsonmicro.main> (raw)
In-Reply-To: <20190118172854.GC6260@sirena.org.uk>
On Fri, Jan 18, 2019 at 05:28:54PM +0000, Mark Brown wrote:
> On Fri, Jan 18, 2019 at 11:36:31AM +0000, Charles Keepax wrote:
> > The module alias has no effect as the driver can only be loaded through
> > device tree at this time.
>
> It also does no harm...
Indeed yes, I have no problem with leaving it.
Thanks,
Charles
prev parent reply other threads:[~2019-01-21 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 11:36 [PATCH 1/2] regulator: lochnagar: Add missing MODULE_DEVICE_TABLE Charles Keepax
2019-01-18 11:36 ` [PATCH 2/2] regulator: lochnagar: Remove redundant MODULE_ALIAS Charles Keepax
2019-01-18 17:28 ` Mark Brown
2019-01-21 9:21 ` Charles Keepax [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=20190121092155.GG3837@imbe.wolfsonmicro.main \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.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).