All of lore.kernel.org
 help / color / mirror / Atom feed
From: jeffy <jeffy.chen@rock-chips.com>
To: Mark Brown <broonie@kernel.org>
Cc: Donglin Peng <dolinux.peng@gmail.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: Mon, 28 Aug 2017 06:21:18 +0800	[thread overview]
Message-ID: <59A345DE.3070302@rock-chips.com> (raw)
In-Reply-To: <20170827143457.tqc73fkhcly7dej2@sirena.org.uk>

hi Mark,

On 08/27/2017 10:34 PM, Mark Brown wrote:
> On Sun, Aug 27, 2017 at 10:31:52PM +0800, Jeffy Chen wrote:
>
> This is a HTML only mail and I have a text only client...
>
sorry, i was replying with my phone, didn't notice it would use html by 
default...

i think you've applied the right version of patch(v3), and the robot is 
warning the v2 version :)

  reply	other threads:[~2017-08-27 22:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24  3:34 [PATCH v2] ASoC: Add a sanity check before using dai driver name 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 14:13   ` kbuild test robot
2017-08-26 15:09   ` Donglin Peng
2017-08-27 12:19     ` Mark Brown
2017-08-27 12:19       ` Mark Brown
2017-08-27 13:54       ` Donglin Peng
2017-08-27 14:26         ` Mark Brown
2017-08-27 14:26           ` Mark Brown
2017-08-27 14:31         ` Jeffy Chen
2017-08-27 14:34           ` Mark Brown
2017-08-27 14:34             ` Mark Brown
2017-08-27 22:21             ` jeffy [this message]
2017-08-28  1:47           ` Donglin Peng
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=59A345DE.3070302@rock-chips.com \
    --to=jeffy.chen@rock-chips.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=dolinux.peng@gmail.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 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.