From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Sameer Pujar <spujar@nvidia.com>,
thierry.reding@gmail.com, jonathanh@nvidia.com,
alsa-devel@alsa-project.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, sharadg@nvidia.com
Subject: Re: [PATCH v2 0/3] Rename audio graph export functions
Date: Fri, 5 Feb 2021 19:24:24 +0000 [thread overview]
Message-ID: <20210205192424.GK4720@sirena.org.uk> (raw)
In-Reply-To: <875z37scr8.wl-kuninori.morimoto.gx@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
On Fri, Feb 05, 2021 at 07:20:42AM +0900, Kuninori Morimoto wrote:
> > This series renames exported functions from audio graph for a better
> > global visibility. In doing so update the references in audio graph
> > and Tegra audio graph card drivers.
> I guess [1/3] and [2/3] should be merged/squashed ?
> Otherwise, there is git-bisect error.
Yes, and I'll complain because I have automation to test every patch
individually! Otherwise this does look fine to me too.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-02-05 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 13:50 [PATCH v2 0/3] Rename audio graph export functions Sameer Pujar
2021-02-04 13:50 ` [PATCH v2 1/3] ASoC: audio-graph: Rename functions needed for export Sameer Pujar
2021-02-04 13:50 ` [PATCH v2 2/3] ASoC: tegra: Update references of audio graph helpers Sameer Pujar
2021-02-04 13:50 ` [PATCH v2 3/3] ASoC: tegra: Add driver remove() callback Sameer Pujar
2021-02-04 22:20 ` [PATCH v2 0/3] Rename audio graph export functions Kuninori Morimoto
2021-02-05 19:24 ` Mark Brown [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=20210205192424.GK4720@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jonathanh@nvidia.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sharadg@nvidia.com \
--cc=spujar@nvidia.com \
--cc=thierry.reding@gmail.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).