From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
Kenneth Westfield <kwestfie@codeaurora.org>
Subject: Re: [PATCH] SoC: Fix MAX98357A codec driver dependencies
Date: Thu, 5 Mar 2015 14:26:31 +0000 [thread overview]
Message-ID: <20150305142631.GN21293@sirena.org.uk> (raw)
In-Reply-To: <54F862B9.1000103@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 252 bytes --]
On Thu, Mar 05, 2015 at 06:05:45AM -0800, Guenter Roeck wrote:
> I notice that the problem this patch is trying to fix is still seen in the
> upstream kernel. Did the patch get lost after all, or is it still in the
> queue ?
My git tree is public...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-03-05 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 21:13 Guenter Roeck
2015-02-12 2:55 ` Mark Brown
2015-03-05 14:05 ` Guenter Roeck
2015-03-05 14:26 ` Mark Brown [this message]
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=20150305142631.GN21293@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kwestfie@codeaurora.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®