From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Greg KH <greg@kroah.com>
Cc: linux-wireless@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH] staging: rtl8192e: Fix incorrect netif_stop_queue usage warning
Date: Tue, 01 Mar 2011 23:43:40 +0200 [thread overview]
Message-ID: <4D6D688C.7090605@pardus.org.tr> (raw)
In-Reply-To: <20110301211523.GA19958@kroah.com>
On 01.03.2011 23:15, Greg KH wrote:
> On Tue, Mar 01, 2011 at 09:23:12AM +0200, Ozan Çağlayan wrote:
>> The TX queues are allocated inside register_netdev.
>> It doesn't make any sense to stop the queue before
>> allocation.
>>
>> Signed-off-by: Ozan Çağlayan<ozan@pardus.org.tr>
>> ---
>> drivers/staging/rtl8192e/r8192E_core.c | 1 -
>> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> This patch doesn't apply, what tree did you make it against?
hmm, weird it was on top of an up-to-date linux-2.6 tree.
--
Pardus Linux
http://www.pardus.org.tr/eng
next prev parent reply other threads:[~2011-03-01 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 7:23 [PATCH] staging: rtl8192e: Fix incorrect netif_stop_queue usage warning Ozan Çağlayan
2011-03-01 21:15 ` Greg KH
2011-03-01 21:43 ` Ozan Çağlayan [this message]
2011-03-01 22:01 ` Greg KH
2011-03-01 22:04 ` Ozan Çağlayan
2011-03-03 12:37 ` Ozan Çağlayan
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=4D6D688C.7090605@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-wireless@vger.kernel.org \
/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.