From: Mark Brown <broonie@kernel.org>
To: David Lin <CTLIN0@nuvoton.com>
Cc: WTLI@nuvoton.com, YHCHuang@nuvoton.com,
alsa-devel@alsa-project.org, KCHSU0@nuvoton.com,
lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: nau8315: add codec driver
Date: Fri, 30 Oct 2020 13:25:48 +0000 [thread overview]
Message-ID: <20201030132548.GB4405@sirena.org.uk> (raw)
In-Reply-To: <20201030050146.535983-1-CTLIN0@nuvoton.com>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
On Fri, Oct 30, 2020 at 01:01:48PM +0800, David Lin wrote:
> Add codec driver for Nuvoton NAU8315.
This has still got issues - it looks like all the tabs in the patch have
been replaced by spaces, that's going to make it impossible for any of
the tools to handle. I'm not sure how your colleagues handled this,
another approach some people use is to send from a non-work account and
bypass all the issues with corporate mail servers :/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-30 13:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 5:01 [PATCH] ASoC: nau8315: add codec driver David Lin
2020-10-30 13:25 ` Mark Brown [this message]
2020-11-01 5:59 ` CTLIN0
-- strict thread matches above, loose matches on Subject: below --
2020-11-02 2:32 David Lin
2020-11-02 14:42 ` Pierre-Louis Bossart
2020-11-04 11:49 ` CTLIN0
2020-11-04 14:51 ` Pierre-Louis Bossart
2020-11-05 2:20 ` Tzung-Bi Shih
2020-11-05 15:02 ` Mark Brown
2020-11-05 16:21 ` Pierre-Louis Bossart
2020-11-06 3:31 ` CTLIN0
2020-11-06 12:20 ` Mark Brown
2020-11-06 14:57 ` Pierre-Louis Bossart
2020-11-10 16:02 ` Mark Brown
2020-10-29 11:33 David Lin
2020-10-29 12:46 ` Mark Brown
2020-10-30 5:00 ` CTLIN0
2020-10-30 12:56 ` 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=20201030132548.GB4405@sirena.org.uk \
--to=broonie@kernel.org \
--cc=CTLIN0@nuvoton.com \
--cc=KCHSU0@nuvoton.com \
--cc=WTLI@nuvoton.com \
--cc=YHCHuang@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--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.