From: Mark Brown <broonie@kernel.org>
To: "jeff_chang(張世佳)" <jeff_chang@richtek.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tiwai@suse.com" <tiwai@suse.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
Jeff Chang <richtek.jeff.chang@gmail.com>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"perex@perex.cz" <perex@perex.cz>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ASoC: Add MediaTek MT6660 Speaker Amp Driver
Date: Tue, 24 Dec 2019 23:51:45 +0000 [thread overview]
Message-ID: <20191224235145.GA27497@sirena.org.uk> (raw)
In-Reply-To: <7a9bcf5d414c4a74ae8e101c54c9e46f@ex1.rt.l>
[-- Attachment #1.1: Type: text/plain, Size: 370 bytes --]
On Mon, Dec 23, 2019 at 02:10:12AM +0000, jeff_chang(張世佳) wrote:
> --> When I check other driver at sound/soc/codecs/ folder, I just follow what others do.
> It seems in .h --> /* SPDX-Liencese-Identifier: GPL-2.0 */
> In .c --> // SPDK-Liencese-Identifier: GPL-2.0
> Is it correct?
Yes, headers use C style comments and source files use C++ style.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-24 23:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 10:15 [PATCH] ASoC: Add MediaTek MT6660 Speaker Amp Driver Jeff Chang
2019-12-20 12:11 ` Mark Brown
[not found] ` <7a9bcf5d414c4a74ae8e101c54c9e46f@ex1.rt.l>
2019-12-24 23:51 ` Mark Brown [this message]
[not found] ` <938f562e322849328d5a7782b2c1de97@ex1.rt.l>
2019-12-25 17:45 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2019-12-12 12:12 Jeff Chang
2019-12-12 14:53 ` Mark Brown
[not found] ` <b0f4c1afd1d341b49b87b7b5cda5ea4d@ex1.rt.l>
2019-12-13 11:32 ` Mark Brown
2019-12-12 11:08 Jeff Chang
2019-12-12 11:57 ` Matthias Brugger
2019-12-12 12:06 ` Mark Brown
2019-12-17 15:17 ` Greg KH
2019-12-12 9:12 Jeff Chang
2019-12-12 10:36 ` Jaroslav Kysela
2019-12-12 8:29 [PATCH] ASoC: add " Jeff Chang
2019-12-12 8:52 ` Matthias Brugger
2019-12-12 6:58 Jeff Chang
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=20191224235145.GA27497@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jeff_chang@richtek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=perex@perex.cz \
--cc=richtek.jeff.chang@gmail.com \
--cc=tiwai@suse.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).