From: Larry Finger <Larry.Finger@lwfinger.net>
To: "\"Paul Rolland (ポール・ロラン)\"" <rol@witbe.net>
Cc: Richard Genoud <richard.genoud@gmail.com>,
Chaoming Li <chaoming_li@realsil.com.cn>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: rtl8192cu: slow path warning
Date: Tue, 23 Jul 2013 10:05:26 -0500 [thread overview]
Message-ID: <51EE9BB6.8000501@lwfinger.net> (raw)
In-Reply-To: <20130723142907.53103aab@tux.DEF.witbe.net>
On 07/23/2013 07:29 AM, Paul Rolland (ポール・ロラン) wrote:
> Hello,
>
> On Thu, 27 Jun 2013 09:33:20 +0200
> Richard Genoud <richard.genoud@gmail.com> wrote:
>
>> Yes, of course, you can add my
>> Reported-by: Richard Genoud <richard.genoud@gmail.com>
>>
>> But the patch doesn't compile on my platform ( since I'm on ARM, I
>> haven't got a PCI bus, so rtlwifi/pci.c is not compiled ) :
>>
>> ERROR: "rtl_lps_change_work_callback"
>> [drivers/net/wireless/rtlwifi/rtlwifi.ko] undefined!
>
> Is that the reason why this patch is not yet in 3.10.x or 3.11-rcY ?
> I'm running a 3.10.1 with USB dongle including 8192CU, and I can see this
> warning when the machine starts.
> I've check 3.10.1, 3.10.2 and 3.11-rc3 source code, but this fix is not
> there. Is there a different fix that went in in 3.10.2 or 3.11-rc?
The reason that patch is not in mainline is that it takes time. If you want to
have it, you can get the official patch from
http://marc.info/?l=linux-wireless&m=137242880222442&w=2, or you need to
implement kernels from the wireless-testing git tree, where it was added on June
28 as commit bcfb879. My original patch included the following note for John
Linville:
"Ideally, this patch should be pushed to the 3.10 stream; however, at this late
time that is not possible. Please push it for 3.11 and the Cc to stable will get
it into 3.10.X."
As you see, it was marked with a Cc for Stable, and it will be propagated to
3.10 when it gets incorporated by Linus. I think I have done all that I can do
for now.
If you want to lobby Linus to get stuff accepted faster, that is your
prerogative; however, I could not recommend that action, and I certainly will
never do anything like that.
Larry
next prev parent reply other threads:[~2013-07-23 15:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 12:38 rtl8192cu: slow path warning and connection problem v3.10-rc5 Richard GENOUD
2013-06-11 13:42 ` Richard Genoud
2013-06-26 14:22 ` rtl8192cu: slow path warning Richard GENOUD
2013-06-26 15:54 ` Larry Finger
2013-06-27 7:33 ` Richard Genoud
2013-06-27 14:38 ` Larry Finger
2013-06-27 18:20 ` Larry Finger
2013-06-28 8:58 ` Richard GENOUD
2013-06-28 13:53 ` Maxime Ripard
2013-06-28 14:16 ` Larry Finger
2013-07-23 12:29 ` Paul Rolland
2013-07-23 14:26 ` Paul Rolland
2013-07-23 15:00 ` Richard Genoud
2013-07-23 15:05 ` Larry Finger [this message]
2013-07-23 15:49 ` Paul Rolland
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=51EE9BB6.8000501@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=richard.genoud@gmail.com \
--cc=rol@witbe.net \
/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
Powered by JetHome