From: Mark Brown <broonie@kernel.org>
To: John Hsu <KCHSU0@nuvoton.com>
Cc: AP MS30 Linux ALSA <alsa-devel@alsa-project.org>,
"anatol.pomozov@gmail.com" <anatol.pomozov@gmail.com>,
AC30 YHChuang <YHCHuang@nuvoton.com>,
AC30 WTLi <WTLI@nuvoton.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"benzh@chromium.org" <benzh@chromium.org>,
AC30 CTLin0 <CTLIN0@nuvoton.com>, MS40 MHKuo <MHKuo@nuvoton.com>,
"yong.zhi@intel.com" <yong.zhi@intel.com>
Subject: Re: [PATCH] ASoC: nau8825: automatic BCLK and LRC divde in master mode
Date: Thu, 16 Feb 2017 12:13:50 +0000 [thread overview]
Message-ID: <20170216121349.q7fa3uwij3ki7t4j@sirena.org.uk> (raw)
In-Reply-To: <58A509A6.1010304@nuvoton.com>
[-- Attachment #1.1: Type: text/plain, Size: 798 bytes --]
On Thu, Feb 16, 2017 at 10:08:38AM +0800, John Hsu wrote:
> On 2/14/2017 7:09 PM, Mark Brown wrote:
> > This patch *still* does not apply. Please, try sending to yourself and
> > applying with git am before you resend to me. Check that the patch is
> > not being corrupted when you send it (things like space/tab conversion
> > for example).
> I have resent the patch to myself. And copy the mail content to a new
> patch. Then try the command as follows, and it seems work fine.
> git am --signoff < ASoC-nau8825-auto-BCLK-and-LRC-divide.patch
I looked again, you've got at least space/tab conversion problems in
there in the copy that ended up in my mailbox. Perhaps there was some
temporary problem in the mail system your company uses, can you try
resending to me and see if it's sorted?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2017-02-16 12:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 5:44 [PATCH] ASoC: nau8825: automatic BCLK and LRC divde in master mode John Hsu
2017-02-14 11:09 ` Mark Brown
2017-02-16 2:08 ` John Hsu
2017-02-16 12:13 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-17 1:55 John Hsu
2017-02-17 10:40 ` Mark Brown
2017-02-17 10:43 ` Mark Brown
2017-02-20 2:32 ` John Hsu
2017-02-20 18:26 ` Mark Brown
2017-02-21 2:17 ` John Hsu
2017-02-09 7:30 John Hsu
2017-02-09 16:45 ` Mark Brown
2017-02-10 1:11 ` John Hsu
2017-02-10 12:05 ` 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=20170216121349.q7fa3uwij3ki7t4j@sirena.org.uk \
--to=broonie@kernel.org \
--cc=CTLIN0@nuvoton.com \
--cc=KCHSU0@nuvoton.com \
--cc=MHKuo@nuvoton.com \
--cc=WTLI@nuvoton.com \
--cc=YHCHuang@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=anatol.pomozov@gmail.com \
--cc=benzh@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=yong.zhi@intel.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.