From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] ASoC: fsl: fix dependencies for wm8962
Date: Wed, 1 Oct 2014 10:51:40 -0700 [thread overview]
Message-ID: <20141001175139.GA5100@Asurada> (raw)
In-Reply-To: <20141001122234.GX4273@sirena.org.uk>
On Wed, Oct 01, 2014 at 01:22:34PM +0100, Mark Brown wrote:
> On Tue, Sep 30, 2014 at 04:26:18PM -0700, Nicolin Chen wrote:
>
> > I checked the Archive, the patch only got one version without cover
> > letter. And this version only got one reply which is the Applied mail.
> > I guess your earlier reply might have been swallowed somehow so I
> > couldn't read it.
>
> No, there were definitely at least two versions.
Sorry if I've really missed something.
And I still can't find any other reply. I sent the patch with
a RFC tag, so I wouldn't ignore any comment to it, especially
the comment from you sir.
>
> > And I think Fabio's suggestion/patch has no problem right?
>
> That is the fix I was asking for.
Is there any other comment against the driver you can remember?
Thank you
Nicolin
WARNING: multiple messages have this Message-ID (diff)
From: nicoleotsuka@gmail.com (Nicolin Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: fsl: fix dependencies for wm8962
Date: Wed, 1 Oct 2014 10:51:40 -0700 [thread overview]
Message-ID: <20141001175139.GA5100@Asurada> (raw)
In-Reply-To: <20141001122234.GX4273@sirena.org.uk>
On Wed, Oct 01, 2014 at 01:22:34PM +0100, Mark Brown wrote:
> On Tue, Sep 30, 2014 at 04:26:18PM -0700, Nicolin Chen wrote:
>
> > I checked the Archive, the patch only got one version without cover
> > letter. And this version only got one reply which is the Applied mail.
> > I guess your earlier reply might have been swallowed somehow so I
> > couldn't read it.
>
> No, there were definitely at least two versions.
Sorry if I've really missed something.
And I still can't find any other reply. I sent the patch with
a RFC tag, so I wouldn't ignore any comment to it, especially
the comment from you sir.
>
> > And I think Fabio's suggestion/patch has no problem right?
>
> That is the fix I was asking for.
Is there any other comment against the driver you can remember?
Thank you
Nicolin
next prev parent reply other threads:[~2014-10-01 17:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 11:43 [PATCH] ASoC: fsl: fix dependencies for wm8962 Arnd Bergmann
2014-09-30 11:43 ` Arnd Bergmann
2014-09-30 16:45 ` Mark Brown
2014-09-30 16:45 ` Mark Brown
2014-09-30 17:38 ` Fabio Estevam
2014-09-30 17:38 ` Fabio Estevam
2014-09-30 19:43 ` Nicolin Chen
2014-09-30 19:43 ` Nicolin Chen
2014-09-30 19:48 ` Fabio Estevam
2014-09-30 19:48 ` Fabio Estevam
2014-09-30 20:37 ` Nicolin Chen
2014-09-30 20:37 ` Nicolin Chen
2014-09-30 17:42 ` Nicolin Chen
2014-09-30 17:42 ` Nicolin Chen
2014-09-30 23:09 ` Mark Brown
2014-09-30 23:09 ` Mark Brown
2014-09-30 23:26 ` Nicolin Chen
2014-09-30 23:26 ` Nicolin Chen
2014-10-01 12:22 ` Mark Brown
2014-10-01 12:22 ` Mark Brown
2014-10-01 17:51 ` Nicolin Chen [this message]
2014-10-01 17:51 ` Nicolin Chen
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=20141001175139.GA5100@Asurada \
--to=nicoleotsuka@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.