From: Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
To: Joe Perches <joe@perches.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>,
<linux-wireless@vger.kernel.org>
Subject: Re: [RFC] mac80211: net_ratelimit few aggregation related messages
Date: Mon, 28 May 2012 12:21:10 +0530 [thread overview]
Message-ID: <4FC3205E.6020608@qca.qualcomm.com> (raw)
In-Reply-To: <1338187439.2202.20.camel@joe2Laptop>
On Monday 28 May 2012 12:13 PM, Joe Perches wrote:
> On Mon, 2012-05-28 at 12:01 +0530, Mohammed Shafi Shajakhan wrote:
>> On Monday 28 May 2012 11:56 AM, Joe Perches wrote:
>>> On Mon, 2012-05-28 at 11:45 +0530, Mohammed Shafi Shajakhan wrote:
>>>> just today saw this link where you had introduced net_dbg_ratelimited
>>>> http://www.digipedia.pl/usenet/thread/18978/31017/
>>>> so should i send the v2 patch using net_dbg_ratelimited to net-next
>>>> rather than wireless-testing tree ?
>>>
>>> Yes, but you should wait until net-next opens
>>> for patches (after Linus' -rc1 is released)
>> Joe, once Linus release rc1, will your changes will be updated in
>> wireless-testing ,
>
> I presume so, the patch is in Linus' tree for 3.4.
>
>> so that i can send a patch directly to John/linux
>> wireless ? thank you.
>
> I guess you'll have to wait for John to merge Linus' tree.
>
sure, thanks!
--
thanks,
shafi
prev parent reply other threads:[~2012-05-28 6:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 15:37 [RFC] mac80211: net_ratelimit few aggregation related messages Mohammed Shafi Shajakhan
2012-05-25 20:02 ` Joe Perches
2012-05-28 6:15 ` Mohammed Shafi Shajakhan
2012-05-28 6:26 ` Joe Perches
2012-05-28 6:31 ` Mohammed Shafi Shajakhan
2012-05-28 6:43 ` Joe Perches
2012-05-28 6:51 ` Mohammed Shafi Shajakhan [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=4FC3205E.6020608@qca.qualcomm.com \
--to=mohammed@qca.qualcomm.com \
--cc=joe@perches.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).