From: Viresh Kumar <viresh.kumar@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: "Lee Jones" <lee.jones@linaro.org>,
"Krzysztof Kozłowski" <k.kozlowski@samsung.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] mfd: wm8994: kenel WARN and crashes
Date: Fri, 9 Sep 2016 15:50:45 +0530 [thread overview]
Message-ID: <20160909102045.GB18547@vireshk-i7> (raw)
In-Reply-To: <20160909101455.GB27946@sirena.org.uk>
On 09-09-16, 11:14, Mark Brown wrote:
> On Fri, Sep 09, 2016 at 02:19:35PM +0530, Viresh Kumar wrote:
>
> > Didn't had much time to investigate and so just reporting the issue
> > for now.
>
> You probably want to contact the wm8994 maintainers regarding issues
> with the wm8994 driver...
Sure, but I couldn't find who the maintainer is. Neither was
MAINTAINERS file of any help, nor was get-maintainers script.
The first commit shows this:
commit 9e50108668a70a9927257298bd4e679300124420
Author: Mark Brown <broonie@opensource.wolfsonmicro.com>
Date: Fri Jan 29 18:20:29 2010 +0000
mfd: Add initial WM8994 support
The WM8994 is a highly integrated ultra low power audio hub CODEC.
Since it includes on-board regulators and GPIOs it is represented
as a multi-function device, though the overwhelming majority of
the functionality is provided by the ASoC CODEC driver.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
Isn't this you?
--
viresh
next prev parent reply other threads:[~2016-09-09 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 8:49 Viresh Kumar
2016-09-09 10:14 ` Mark Brown
2016-09-09 10:20 ` Viresh Kumar [this message]
2016-09-09 11:21 ` Mark Brown
2016-09-09 11:42 ` Joe Perches
2016-09-09 11:49 ` Mark Brown
2016-09-09 11:58 ` Joe Perches
2016-09-09 12:03 ` Mark Brown
2016-09-09 11:22 ` Mark Brown
2016-09-09 11:26 ` Viresh Kumar
2016-09-09 11:25 ` Viresh Kumar
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=20160909102045.GB18547@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=broonie@kernel.org \
--cc=k.kozlowski@samsung.com \
--cc=lee.jones@linaro.org \
--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
all inboxes | Powered by JetHome®