From: Tony Lindgren <tony@atomide.com>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org,
Rajendra Nayak <rnayak@ti.com>,
Benoit Cousson <bcousson@baylibre.com>,
Paolo Pisati <p.pisati@gmail.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] ARM: dts: Fix muxing and regulator for wl12xx on the SDIO bus for pandaboard
Date: Tue, 17 Sep 2013 17:02:05 -0700 [thread overview]
Message-ID: <20130918000203.GS9994@atomide.com> (raw)
In-Reply-To: <1379399290.4223.124.camel@porter.coelho.fi>
* Luca Coelho <luca@coelho.fi> [130916 23:35]:
> On Tue, 2013-09-17 at 09:26 +0300, Luca Coelho wrote:
> > Both patches look good to me, though I didn't have the time to retest
> > them.
>
> Actually I don't even have a Blaze device anymore, so I can't really
> test the second patch. :(
OK no problem, I've tested it on panda es.
Regards,
Tony
next prev parent reply other threads:[~2013-09-18 0:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 19:09 [PATCH 0/2] WLAN regression fixes for omap4 after moving to DT based booting Tony Lindgren
2013-09-13 19:09 ` [PATCH 1/2] ARM: dts: Fix muxing and regulator for wl12xx on the SDIO bus for pandaboard Tony Lindgren
2013-09-17 6:26 ` Luca Coelho
2013-09-17 6:28 ` Luca Coelho
2013-09-18 0:02 ` Tony Lindgren [this message]
2013-09-18 9:04 ` Benoit Cousson
2013-09-18 17:51 ` Tony Lindgren
2013-09-18 23:47 ` Tony Lindgren
2013-09-19 5:43 ` Luca Coelho
2013-09-19 14:53 ` Tony Lindgren
2013-09-19 17:21 ` Luca Coelho
2013-09-18 23:57 ` Olof Johansson
2013-09-13 19:09 ` [PATCH 2/2] ARM: dts: Fix muxing and regulator for wl12xx on the SDIO bus for blaze Tony Lindgren
2013-09-14 5:10 ` [PATCH 0/2] WLAN regression fixes for omap4 after moving to DT based booting Olof Johansson
2013-09-16 21:38 ` Tony Lindgren
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=20130918000203.GS9994@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=luca@coelho.fi \
--cc=p.pisati@gmail.com \
--cc=rnayak@ti.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).