From: Mark Brown <broonie@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Clemens Gruber <clemens.gruber@pqgruber.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Eric Nelson <eric@nelint.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: sgtl5000: only check VDDD-supply, not revision
Date: Thu, 2 Jun 2016 17:56:51 +0100 [thread overview]
Message-ID: <20160602165651.GP2282@sirena.org.uk> (raw)
In-Reply-To: <CAOMZO5B20n7Tu3r+BsU2R5BbYj41tf7qBsMLRWxChdWMkHxLNQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 301 bytes --]
On Thu, Jun 02, 2016 at 12:48:15PM -0300, Fabio Estevam wrote:
> Sometime ago you were looking at this. What do you think about this patch?
I'm rather concerned that the patches came from people working closely
with Freescale already - are we *sure* that Freescale/NXP's public
errata are accurate?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-06-02 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 12:47 [PATCH] ASoC: sgtl5000: only check VDDD-supply, not revision Clemens Gruber
2016-06-02 15:48 ` Fabio Estevam
2016-06-02 16:56 ` Mark Brown [this message]
2016-06-03 15:52 ` Clemens Gruber
2016-06-03 16:23 ` Eric Nelson
2016-06-04 5:18 ` Eric Nelson
2016-06-04 9:03 ` Clemens Gruber
[not found] ` <20160604171525.GA29266@archie.localdomain>
2016-06-05 23:16 ` [alsa-devel] " Clemens Gruber
2016-06-06 1:22 ` Fabio Estevam
2016-06-06 16:45 ` Clemens Gruber
2016-06-06 17:10 ` Fabio Estevam
2016-06-06 17:55 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2016-05-31 19:11 Clemens Gruber
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=20160602165651.GP2282@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=clemens.gruber@pqgruber.com \
--cc=eric@nelint.com \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox