From: "Kenneth Westfield" <kwestfie@codeaurora.org>
To: Mark Brown <broonie@kernel.org>
Cc: Kenneth Westfield <kwestfie@codeaurora.org>,
Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lgirdwood@gmail.com>,
David Brown <davidb@codeaurora.org>,
Bryan Huntsman <bryanh@codeaurora.org>,
Rob Herring <rob.herring@calxeda.com>,
Greg KH <gregkh@linuxfoundation.org>,
Patrick Lai <plai@codeaurora.org>,
Banajit Goswami <bgoswami@codeaurora.org>,
ALSA Mailing List <alsa-devel@alsa-project.org>,
Device Tree Mailing List <devicetree@vger.kernel.org>,
MSM Mailing List <linux-arm-msm@vger.kernel.org>
Subject: Re: [Patch v2 02/11] ASoC: qcom: Add device tree binding docs
Date: Thu, 11 Dec 2014 00:23:55 -0800 [thread overview]
Message-ID: <fdc53daed0c7c41168a14de6b2983895.squirrel@www.codeaurora.org> (raw)
On Tue, December 9, 2014 7:37 am, Mark Brown wrote:
> On Mon, Dec 08, 2014 at 02:01:04PM -0800, Kenneth Westfield wrote:
>> From: Kenneth Westfield <kwestfie@codeaurora.org>
>> Add documentation to the sound directory of the
>> device-tree bindings for IPQ806x audio drivers.
> Please don't send multiple separate changes in a single patch. One change per patch.
In an effort to reduce the number of patches, would it be possible to package the DT doc with its
respective driver in one patch? Or does the DT doc need to be in a patch by itself? I've seen
examples of both.
Also, I will combine the partial addition of each driver to its respective Kconfig/Makefile
entries. For this, I believe I need to start with an empty Kconfig/Makefile in the first patch?
--
Kenneth Westfield
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation
Collaborative Project
next reply other threads:[~2014-12-11 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 8:23 Kenneth Westfield [this message]
2014-12-11 13:15 ` [Patch v2 02/11] ASoC: qcom: Add device tree binding docs Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2014-12-08 22:01 [Patch v2 00/11] ASoC: QCOM: Add support for ipq806x SOC Kenneth Westfield
2014-12-08 22:01 ` [Patch v2 02/11] ASoC: qcom: Add device tree binding docs Kenneth Westfield
2014-12-09 15:37 ` 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=fdc53daed0c7c41168a14de6b2983895.squirrel@www.codeaurora.org \
--to=kwestfie@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=broonie@kernel.org \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=plai@codeaurora.org \
--cc=rob.herring@calxeda.com \
--cc=tiwai@suse.de \
/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).