From: Panduranga <x0125717@ti.com>
To: <tony@atomide.com>
Cc: <ohad@wizery.com>, "Gabay, Benzy" <benzyg@ti.com>,
"Gurumath, Pradeep" <pradeepgurumath@ti.com>,
"Mahaveer, Vishal" <vishalm@ti.com>,
"Boudet, Xavier" <x-boudet@ti.com>,
"Jain, Naveen" <naveen_jain@ti.com>,
"Halli, Manjunatha" <manjunatha_halli@ti.com>,
"Mallireddy, Panduranga" <panduranga_mallireddy@ti.com>,
"Coelho, Luciano" <coelho@ti.com>, <netdev@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 0/1] OMAP: wlan : To fix wlan issue with kernel 3.0
Date: Thu, 11 Aug 2011 12:45:07 +0530 [thread overview]
Message-ID: <606B2926D61D49379AEF49D407C6C912@MINX0125717> (raw)
In-Reply-To: 1311950476-2452-1-git-send-email-panduranga_mallireddy@ti.com
Hi Tony,
Can you merge this patch series to Kernel 3.1.
It fixes the WLAN issue on Panda board, reported in Kernel 3.0
Regards,
Pandu.
----- Original Message -----
From: "Mallireddy, Panduranga" <panduranga_mallireddy@ti.com>
To: "Coelho, Luciano" <coelho@ti.com>; <netdev@vger.kernel.org>;
<linux-omap@vger.kernel.org>; <linux-mmc@vger.kernel.org>
Cc: <ohad@wizery.com>; "Gabay, Benzy" <benzyg@ti.com>; "Gurumath, Pradeep"
<pradeepgurumath@ti.com>; "Mahaveer, Vishal" <vishalm@ti.com>; "Boudet,
Xavier" <x-boudet@ti.com>; "Jain, Naveen" <naveen_jain@ti.com>; "Halli,
Manjunatha" <manjunatha_halli@ti.com>; "Mallireddy, Panduranga"
<panduranga_mallireddy@ti.com>
Sent: Friday, July 29, 2011 8:11 PM
Subject: [PATCH 0/1] OMAP: wlan : To fix wlan issue with kernel 3.0
From: Panduranga Mallireddy <panduranga_mallireddy@ti.com>
Error reported for wl12xx driver with Kernel 3.0 is
[ 0.181457] error setting wl12xx data
FIX:
For regulator omap4_clk32k used by wlan, set .constraints.always_on to 1
Panduranga Mallireddy (1):
OMAP: wlan: Set the WLAN Regulator to be always on
arch/arm/mach-omap2/twl-common.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
parent reply other threads:[~2011-08-11 7:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1311950476-2452-1-git-send-email-panduranga_mallireddy@ti.com>]
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=606B2926D61D49379AEF49D407C6C912@MINX0125717 \
--to=x0125717@ti.com \
--cc=benzyg@ti.com \
--cc=coelho@ti.com \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=manjunatha_halli@ti.com \
--cc=naveen_jain@ti.com \
--cc=netdev@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=panduranga_mallireddy@ti.com \
--cc=pradeepgurumath@ti.com \
--cc=tony@atomide.com \
--cc=vishalm@ti.com \
--cc=x-boudet@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).