From: Mark Brown <broonie@kernel.org>
To: Rohit Kumar <rohitkr@codeaurora.org>
Cc: Ajit Pandey <ajitp@codeaurora.org>,
devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
bgoswami@codeaurora.org, plai@codeaurora.org,
linux-kernel@vger.kernel.org, srinivas.kandagatla@linaro.org
Subject: Re: [PATCH v2 1/7] Documentation: device-tree: sound: Update lpass-cpu driver binding
Date: Mon, 6 Jul 2020 12:44:03 +0100 [thread overview]
Message-ID: <20200706114403.GA6176@sirena.org.uk> (raw)
In-Reply-To: <f44e2526-3497-7900-0db6-39b6b5af2d9b@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
On Mon, Jul 06, 2020 at 04:59:39PM +0530, Rohit Kumar wrote:
> @Mark, I was planning to post v3 patchset series for this and keep yaml
> change as
My name is Mark.
> driver change will have checkpatch errors. Can you please suggest if should
> make
> first Documentation change in text file itself before driver change and
> finally have a
> patch to convert it to yaml at the end?
As ever make the YAML conversion the very last thing you do in your
series so it doesn't hold anything else up.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Rohit Kumar <rohitkr@codeaurora.org>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
bgoswami@codeaurora.org, plai@codeaurora.org,
Ajit Pandey <ajitp@codeaurora.org>,
linux-kernel@vger.kernel.org, srinivas.kandagatla@linaro.org
Subject: Re: [PATCH v2 1/7] Documentation: device-tree: sound: Update lpass-cpu driver binding
Date: Mon, 6 Jul 2020 12:44:03 +0100 [thread overview]
Message-ID: <20200706114403.GA6176@sirena.org.uk> (raw)
In-Reply-To: <f44e2526-3497-7900-0db6-39b6b5af2d9b@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
On Mon, Jul 06, 2020 at 04:59:39PM +0530, Rohit Kumar wrote:
> @Mark, I was planning to post v3 patchset series for this and keep yaml
> change as
My name is Mark.
> driver change will have checkpatch errors. Can you please suggest if should
> make
> first Documentation change in text file itself before driver change and
> finally have a
> patch to convert it to yaml at the end?
As ever make the YAML conversion the very last thing you do in your
series so it doesn't hold anything else up.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-06 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 11:29 [PATCH v2 1/7] Documentation: device-tree: sound: Update lpass-cpu driver binding Rohit Kumar
2020-07-06 11:44 ` Mark Brown [this message]
2020-07-06 11:44 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2020-05-16 17:37 Ajit Pandey
2020-05-16 17:37 ` Ajit Pandey
[not found] <“1586592171-31644-1-git-send-email-ajitp@codeaurora.org”>
2020-05-14 16:38 ` [PATCH v2 0/7] ASoC: QCOM: Add support for SC7180 lpass variant Ajit Pandey
2020-05-14 16:38 ` [PATCH v2 1/7] Documentation: device-tree: sound: Update lpass-cpu driver binding Ajit Pandey
2020-05-14 16:44 ` 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=20200706114403.GA6176@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ajitp@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plai@codeaurora.org \
--cc=rohitkr@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.