From: Mark Brown <broonie@kernel.org>
To: KaiChieh Chuang <kaichieh.chuang@mediatek.com>
Cc: alsa-devel@alsa-project.org, ryder.lee@mediatek.com,
wsd_upstream@mediatek.com, chipeng.chang@mediatek.com,
garlic.tseng@mediatek.com, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 1/2] ASoC: mt6797: switch to SPDX license tag
Date: Fri, 27 Apr 2018 11:41:21 +0100 [thread overview]
Message-ID: <20180427104121.GB6872@sirena.org.uk> (raw)
In-Reply-To: <20180427015445.4334-2-kaichieh.chuang@mediatek.com>
[-- Attachment #1.1: Type: text/plain, Size: 187 bytes --]
On Fri, Apr 27, 2018 at 09:54:44AM +0800, KaiChieh Chuang wrote:
> sound/soc/mediatek/mt6797/mt6797-afe-clk.c | 21 ++++++---------------
This file doesn't seem to be in -next?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-04-27 10:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 1:54 [PATCH v2 0/2] ASoC: mt6797-mt6351: switch to SPDX license tag KaiChieh Chuang
[not found] ` <20180427015445.4334-1-kaichieh.chuang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-04-27 1:54 ` [PATCH v2 1/2] ASoC: mt6797: " KaiChieh Chuang
2018-04-27 9:15 ` Matthias Brugger
2018-04-27 9:23 ` Sean Wang
2018-04-27 9:27 ` Matthias Brugger
2018-04-27 9:28 ` Sean Wang
2018-04-27 10:41 ` Mark Brown [this message]
2018-04-27 10:55 ` Mark Brown
2018-04-27 10:53 ` Applied "ASoC: mt6797: switch to SPDX license tag" to the asoc tree Mark Brown
2018-04-27 1:54 ` [PATCH v2 2/2] ASoC: mt6351 switch to SPDX license tag KaiChieh Chuang
[not found] ` <20180427015445.4334-3-kaichieh.chuang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-04-27 10:53 ` Applied "ASoC: mt6351 switch to SPDX license tag" to the asoc tree 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=20180427104121.GB6872@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=chipeng.chang@mediatek.com \
--cc=garlic.tseng@mediatek.com \
--cc=kaichieh.chuang@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=ryder.lee@mediatek.com \
--cc=wsd_upstream@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