From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Lee Jones" <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
"Samuel Ortiz" <sameo@linux.intel.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.de>
Subject: Re: [PATCH 1/2] mfd: mc13xxx: Do not use platform data with devicetree
Date: Fri, 09 May 2014 17:56:09 +0400 [thread overview]
Message-ID: <1399643769.716496780@f345.i.mail.ru> (raw)
In-Reply-To: <20140509113030.GV5767@lee--X1>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 956 bytes --]
Fri, 9 May 2014 12:30:30 +0100 от Lee Jones <lee.jones@linaro.org>:
> > This patch removes platform data usage for codec and touchscreen
> > when driver is used with devicetree.
> > This fixes possible "null pointer dereference" error if DTS uses
> > "fsl,mc13xxx-uses-codec" or "fsl,mc13xxx-uses-touch" options.
> >
> > Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
> > ---
> > drivers/mfd/mc13xxx-core.c | 18 ++++++++++--------
> > 1 file changed, 10 insertions(+), 8 deletions(-)
>
> Applied, thanks.
This patch has been written as a way to separate MFD and ASoC changes of
the patch: (ASoC: mc13783: Add devicetree support)
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=780aaeff96819ca58e0cad830bfbe6eee9aef82c
So, it should produce conflict.
---
ÿôèº{.nÇ+‰·Ÿ®‰†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(階ŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥
next prev parent reply other threads:[~2014-05-09 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 6:48 [PATCH 1/2] mfd: mc13xxx: Do not use platform data with devicetree Alexander Shiyan
2014-05-09 11:30 ` Lee Jones
2014-05-09 13:56 ` Alexander Shiyan [this message]
2014-05-09 14:18 ` Lee Jones
2014-05-09 14:30 ` Mark Brown
2014-05-09 14:36 ` Lee Jones
2014-05-09 14:48 ` 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=1399643769.716496780@f345.i.mail.ru \
--to=shc_work@mail.ru \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sameo@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).