From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: Luciano Coelho <coelho@ti.com>,
mark.rutland@arm.com, nm@ti.com, mturquette@linaro.org,
linux-doc@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
linux-wireless@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, "Nori,
Sekhar" <nsekhar@ti.com>,
kernel list <linux-kernel@vger.kernel.org>,
balbi@ti.com, martinez.javier@gmail.com, rob.herring@calxeda.com,
grant.likely@linaro.org, linux-omap@vger.kernel.org,
luca@coelho.fi,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 0/8] wilink: add device tree support
Date: Fri, 28 Feb 2014 10:22:03 +0100 [thread overview]
Message-ID: <20140228092203.GA2974@piout.net> (raw)
In-Reply-To: <CAGm1_kvdzkvzEEymQ+H0XiKugifHF27KDz3jwX5Frg_U=S7KgA@mail.gmail.com>
On 28/02/2014 at 08:26:46 +0100, Yegor Yefremov wrote :
>
> What is the state of the series? Who is now responsible for the
> patches? What issues were still not handled?
>
We probably want to end that discussion before taking those bindings in:
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-February/232185.html
I've hit the issue, precisely using those bindings.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-28 9:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 13:04 [PATCH v4 0/8] wilink: add device tree support Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 1/8] wl1251: split wl251 platform data to a separate structure Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 2/8] wlcore: set irq_flags in the board files instead of hiding behind a quirk Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 3/8] wlcore: remove pwr_in_suspend from platform data Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 4/8] wl12xx: use frequency instead of enumerations for pdata clocks Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 5/8] wlcore: add initial device tree support to the sdio module Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 6/8] wlcore: sdio: add wilink clock providers Luciano Coelho
2013-07-30 22:35 ` Mike Turquette
2013-07-30 23:04 ` Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 7/8] wlcore: sdio: get clocks from device tree Luciano Coelho
2013-07-30 13:04 ` [PATCH v4 8/8] wlcore/wl12xx: check if we got correct clock data from DT Luciano Coelho
2014-02-28 7:26 ` [PATCH v4 0/8] wilink: add device tree support Yegor Yefremov
2014-02-28 9:22 ` Alexandre Belloni [this message]
2014-03-06 10:51 ` Yegor Yefremov
2014-02-28 12:29 ` Luca Coelho
2014-02-28 14:12 ` Luca Coelho
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=20140228092203.GA2974@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=balbi@ti.com \
--cc=coelho@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
--cc=mark.rutland@arm.com \
--cc=martinez.javier@gmail.com \
--cc=mturquette@linaro.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=rob.herring@calxeda.com \
--cc=tony@atomide.com \
--cc=yegorslists@googlemail.com \
/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).