From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: sathyanarayana.nujella@intel.com, fred.oh@linux.intel.com,
cezary.rojewski@intel.com, dharageswari.r@intel.com,
kai.vehmanen@linux.intel.com, kuninori.morimoto.gx@renesas.com,
linux-kernel@vger.kernel.org, yang.jie@linux.intel.com,
tiwai@suse.com, liam.r.girdwood@linux.intel.com,
tzungbi@google.com, ranjani.sridharan@linux.intel.com,
Zou Wei <zou_wei@huawei.com>,
alsa-devel@alsa-project.org, brent.lu@intel.com,
yong.zhi@intel.com
Subject: Re: [PATCH -next] ASoC: intel/boards: add missing MODULE_DEVICE_TABLE
Date: Wed, 12 May 2021 11:25:53 -0500 [thread overview]
Message-ID: <b2873226-4505-5a7b-74ce-95e8d4dd72b5@linux.intel.com> (raw)
In-Reply-To: <20210512155318.GA54562@sirena.org.uk>
>> I wonder if this MODULE_DEVICE_TABLE generates the alias automatically,
>> which would make the existing ones added manually at the end of the files
>> unnecessary? If that was the case, then we should remove those MODULE_ALIAS
>> as well, no?
>
> Yes, you shouldn't need the MODULE_ALIAS stuff there.
ok, if that's alright with everyone I'll send a larger patchset that
correct this for all machine drivers, and add the following two tags to
give proper credits to the reporters.
Reported-by: Hulk Robot <hulkci@huawei.com>
Suggested-by: Zou Wei <zou_wei@huawei.com>
next prev parent reply other threads:[~2021-05-12 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 3:54 [PATCH -next] ASoC: intel/boards: add missing MODULE_DEVICE_TABLE Zou Wei
2021-05-12 13:41 ` Pierre-Louis Bossart
2021-05-12 15:53 ` Mark Brown
2021-05-12 16:25 ` Pierre-Louis Bossart [this message]
2021-05-14 15:22 ` 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=b2873226-4505-5a7b-74ce-95e8d4dd72b5@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=brent.lu@intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=dharageswari.r@intel.com \
--cc=fred.oh@linux.intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sathyanarayana.nujella@intel.com \
--cc=tiwai@suse.com \
--cc=tzungbi@google.com \
--cc=yang.jie@linux.intel.com \
--cc=yong.zhi@intel.com \
--cc=zou_wei@huawei.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).