All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: AC30 CTLin0 <ctlin0@nuvoton.com>
Cc: YHCHuang@nuvoton.com, alsa-devel@alsa-project.org,
	John Hsu <KCHSU0@nuvoton.com>,
	lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: nau8822: new codec driver
Date: Thu, 27 Sep 2018 22:22:21 +0100	[thread overview]
Message-ID: <20180927212221.GY20825@sirena.org.uk> (raw)
In-Reply-To: <26ac5971-f05b-77e7-c3a5-4fd799fcd64b@nuvoton.com>


[-- Attachment #1.1: Type: text/plain, Size: 527 bytes --]

On Thu, Sep 27, 2018 at 06:44:45PM +0800, AC30 CTLin0 wrote:
> OK, I will resend a new patch.
> 
> However, from my last patch file, I can see DT file where is located at
> "Documentation/devicetree/bindings/sound/nau8822.txt".
> 
> And don't you see any DT file?

Ah, that's weird - I'd not expect the binding to have been applied for a
new driver without the code.  In that case everything is fine and no
need to send them again, perhaps just add a note saying that the binding
is already there in case I forget.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2018-09-27 21:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 11:04 [PATCH] ASoC: nau8822: new codec driver David Lin
     [not found] ` <5BA06283.9000801@nuvoton.com>
     [not found]   ` <4c0cc49b-2426-2f5e-028c-f161f2e6553e@nuvoton.com>
     [not found]     ` <20180925165613.GO20825@sirena.org.uk>
     [not found]       ` <20180925175247.GA18430@sirena.org.uk>
2018-09-27 10:44         ` AC30 CTLin0
2018-09-27 21:22           ` Mark Brown [this message]
2018-09-28  3:10 David Lin
2018-10-17 18:54 ` Mark Brown
2018-10-19  4:56   ` AC30 CTLin0
2018-10-19 10:00     ` 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=20180927212221.GY20825@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=KCHSU0@nuvoton.com \
    --cc=YHCHuang@nuvoton.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=ctlin0@nuvoton.com \
    --cc=lgirdwood@gmail.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 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.