From: Mark Brown <broonie@kernel.org>
To: Donglin Peng <dolinux.peng@gmail.com>
Cc: Jeffy Chen <jeffy.chen@rock-chips.com>,
kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org, tiwai@suse.de,
Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH v2] ASoC: Add a sanity check before using dai driver name
Date: Sun, 27 Aug 2017 15:26:17 +0100 [thread overview]
Message-ID: <20170827142617.ddavw3tip2ufaeui@sirena.org.uk> (raw)
In-Reply-To: <CAErzpmvF_N5fskRQe7yv9JsyYXKqG6u5R55B2q5RmAB-i_b7LQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 518 bytes --]
On Sun, Aug 27, 2017 at 09:54:09PM +0800, Donglin Peng wrote:
> On Sun, Aug 27, 2017 at 8:19 PM, Mark Brown <broonie@kernel.org> wrote:
> > Please send incremental fixes rather than new versions for things that
> > are are already applied.
> You should send a incremental patch rather than v3 patch, because your
> v2 patch had been applied and caused this issue.
Right, so I actually just looked at this and I think the right thing got
applied as everything seems to be building fine but I could be confused
here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-08-27 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 3:34 Jeffy Chen
2017-08-24 3:46 ` Donglin Peng
2017-08-24 4:44 ` jeffy
2017-08-26 14:13 ` kbuild test robot
2017-08-26 15:09 ` Donglin Peng
2017-08-27 12:19 ` Mark Brown
2017-08-27 13:54 ` Donglin Peng
2017-08-27 14:26 ` Mark Brown [this message]
[not found] ` <c8fut2564q2ilhtdm8q39a40.1503844312370@email.android.com>
2017-08-27 14:34 ` Mark Brown
2017-08-27 22:21 ` jeffy
2017-08-28 1:47 ` Donglin Peng
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=20170827142617.ddavw3tip2ufaeui@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=dolinux.peng@gmail.com \
--cc=jeffy.chen@rock-chips.com \
--cc=kbuild-all@01.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®