From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: alsa-devel@alsa-project.org, vinod.koul@linaro.org,
tiwai@suse.de, linux-kernel@vger.kernel.org, vkoul@kernel.org,
broonie@kernel.org, srinivas.kandagatla@linaro.org,
sanyog.r.kale@intel.com, bard.liao@intel.com
Subject: Re: [PATCH 2/2] soundwire: Intel: add trigger callback
Date: Fri, 10 Jun 2022 09:53:57 -0500 [thread overview]
Message-ID: <0c493f72-de7f-4c57-f1d5-47f982abc3c8@linux.intel.com> (raw)
In-Reply-To: <YqLV7qexsdhCI7ZZ@kroah.com>
> Where is the in-kernel user of this new callback? Without that, there
> is no need for this, NOR is there a way to properly review this commit.
>
> sorry,
ASoC/SOF will be the user, this is a dependency before Mark Brown can
take additional code in his tree. It was spelled out in the cover letter.
To be clearer, the ONLY user of all the soundwire:intel code is
precisely the ASoC/SOF driver.
next prev parent reply other threads:[~2022-06-10 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 2:35 [PATCH 0/2] " Bard Liao
2022-06-10 2:35 ` [PATCH 1/2] soundwire: intel: uniquify debug message Bard Liao
2022-06-10 5:25 ` Greg KH
2022-06-10 15:06 ` Pierre-Louis Bossart
2022-06-11 7:20 ` Greg KH
2022-06-13 12:48 ` Pierre-Louis Bossart
2022-06-13 17:21 ` Greg KH
2022-06-13 19:21 ` Pierre-Louis Bossart
2022-06-10 2:35 ` [PATCH 2/2] soundwire: Intel: add trigger callback Bard Liao
2022-06-10 5:26 ` Greg KH
2022-06-10 14:53 ` Pierre-Louis Bossart [this message]
2022-06-14 7:13 ` Liao, Bard
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=0c493f72-de7f-4c57-f1d5-47f982abc3c8@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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
all inboxes | Powered by JetHome®