From: sugar <sugar.zhang@rock-chips.com>
To: Mark Brown <broonie@kernel.org>
Cc: heiko@sntech.de, Jaroslav Kysela <perex@perex.cz>,
devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
linux-rockchip@lists.infradead.org,
Oder Chiou <oder_chiou@realtek.com>,
linux-kernel@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Pawel Moll <pawel.moll@arm.com>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Bard Liao <bardliao@realtek.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 0/2] patches to add support for rockchip rt5640 card
Date: Tue, 23 Feb 2016 08:57:04 +0800 [thread overview]
Message-ID: <56CBAE60.6000806@rock-chips.com> (raw)
In-Reply-To: <20160222110416.GC18327@sirena.org.uk>
在 2/22/2016 19:04, Mark Brown 写道:
> On Mon, Feb 22, 2016 at 03:56:53PM +0800, Sugar Zhang wrote:
>
>> Sugar Zhang (2):
>> ASoC: rockchip: i2s: add default values for registers
>> ASoC: rt5640: add master clock handling for rt5640
>
> These appear to be commpletly unrelated patches so should each be sent
> individually rather than as a series - that way there is no confusion
> about them possibly depending on each other and they are easier to
> review and apply.
>
Got it, thanks.
prev parent reply other threads:[~2016-02-23 0:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 7:56 [PATCH v1 0/2] patches to add support for rockchip rt5640 card Sugar Zhang
2016-02-22 7:56 ` [PATCH v1 1/2] ASoC: rockchip: i2s: add default values for registers Sugar Zhang
2016-02-22 7:56 ` [PATCH v1 2/2] ASoC: rt5640: add master clock handling for rt5640 Sugar Zhang
2016-02-22 11:04 ` [PATCH v1 0/2] patches to add support for rockchip rt5640 card Mark Brown
2016-02-23 0:57 ` sugar [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=56CBAE60.6000806@rock-chips.com \
--to=sugar.zhang@rock-chips.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=oder_chiou@realtek.com \
--cc=pawel.moll@arm.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.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).