linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul Rolland" <rol@witbe.net>
To: Larry Finger <Larry.Finger@lwfinger.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,
	rol@witbe.net
Subject: Re: rtl8192cu: slow path warning
Date: Tue, 23 Jul 2013 17:49:04 +0200	[thread overview]
Message-ID: <20130723174904.00d6fab4@tux.DEF.witbe.net> (raw)
In-Reply-To: <51EE9BB6.8000501@lwfinger.net>

[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]

Hello Larry,

On Tue, 23 Jul 2013 10:05:26 -0500
Larry Finger <Larry.Finger@lwfinger.net> wrote:

> 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.

Neither will I... I was just wondering and asking, nothing else, as I'm
also facing this warning. 

I'm glad to see the link you sent is presenting a patch that is the same as
the one I prepared. I'm going to use that while waiting for the patch to
hit mainline !

Thanks for replying, 
Best,
Paul


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2013-07-23 15:51 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
2013-07-23 15:49           ` Paul Rolland [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=20130723174904.00d6fab4@tux.DEF.witbe.net \
    --to=rol@witbe.net \
    --cc=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 \
    /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).