From: Tony Lindgren <tony@atomide.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
l-o List <linux-omap@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"Chikkature Rajashekar, Madhusudhan" <madhu.cr@ti.com>,
"cjb@laptop.org" <cjb@laptop.org>, Luciano Coelho <coelho@ti.com>
Subject: Re: Setting MMC_CAP_POWER_OFF_CARD on mmc2 leads to filesystem problems on mmc1
Date: Wed, 2 Feb 2011 17:08:49 -0800 [thread overview]
Message-ID: <20110203010849.GK3322@atomide.com> (raw)
In-Reply-To: <AANLkTik_pkpe=d4QyLdVmtbvGKTk+k1beRrzKXyeMAND@mail.gmail.com>
* Ohad Ben-Cohen <ohad@wizery.com> [110202 00:00]:
> On Wed, Feb 2, 2011 at 2:11 AM, Tony Lindgren <tony@atomide.com> wrote:
> > * Ohad Ben-Cohen <ohad@wizery.com> [110122 07:47]:
> >> On Sat, Jan 22, 2011 at 5:30 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >> > That was indeed the problem, not I get:
> >> >
> >> > [ 35.417053] wl1271: firmware booted (Rev 6.1.0.0.343)
> >> >
> >> > and
> >> >
> >> > root@beagleboard-xm-next:~# ifconfig wlan0 hw eth 00:11:22:33:44:55
> >> > root@beagleboard-xm-next:~# iwlist wlan0 scanning | grep ESSID | wc -l
> >> > 13
> >> >
> >> > That get's me a lot further!
> >>
> >> Cool !
> >
> > Hmm, do we need to still patch something for the -rc cycle for this?
>
> I don't think so; the problem wasn't in the existing mainline code,
> but in the new functionality developed (adding support for the
> beagletoy expansion board), so this is not -rc material.
OK thanks.
Tony
prev parent reply other threads:[~2011-02-03 1:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 14:18 Setting MMC_CAP_POWER_OFF_CARD on mmc2 leads to filesystem problems on mmc1 Koen Kooi
2011-01-21 14:49 ` Luciano Coelho
2011-01-22 10:36 ` Ohad Ben-Cohen
2011-01-22 15:30 ` Koen Kooi
2011-01-22 15:47 ` Ohad Ben-Cohen
2011-02-02 0:11 ` Tony Lindgren
2011-02-02 8:01 ` Ohad Ben-Cohen
2011-02-03 1:08 ` Tony Lindgren [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=20110203010849.GK3322@atomide.com \
--to=tony@atomide.com \
--cc=cjb@laptop.org \
--cc=coelho@ti.com \
--cc=koen@dominion.thruhere.net \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
--cc=ohad@wizery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.