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>,
Mohammed Shafi Shajakhan <mohammed@qca.qualcomm.com>
Subject: Re: [PATCH] mac80211: ratelimit few aggregated messages
Date: Wed, 13 Jun 2012 10:29:24 +0530 [thread overview]
Message-ID: <4FD81E2C.1000507@qca.qualcomm.com> (raw)
In-Reply-To: <1339098774.14838.4.camel@joe2Laptop>
Hi Joe,
On Friday 08 June 2012 01:22 AM, Joe Perches wrote:
> On Thu, 2012-06-07 at 14:08 +0530, Mohammed Shafi Shajakhan wrote:
>> On Thursday 07 June 2012 01:27 PM, Joe Perches wrote:
>>> On Thu, 2012-06-07 at 13:07 +0530, Mohammed Shafi Shajakhan wrote:
>>>> what about the other wiphy_debug messages, we would
>>>> still retain them know
>>>
>>> Yes, and...
>>>
>>> No, you know those should now still be wiphy_debug
>>> unless the message is HT related and need a new change.
>>
>> sure. so lets drop this patch and do that generic stuff.
>
> I did a little while ago.
> Please modify the patch based on wireless-next commit d63e9ae3b12
sorry for the delayed reply. so you had already posted the change you
had suggested in (netdev@vger.kernel.org mailing list ?) and i have to
do any changes based on that patch right ? thank you!
--
thanks,
shafi
next prev parent reply other threads:[~2012-06-13 4:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 6:02 [PATCH] mac80211: ratelimit few aggregated messages Mohammed Shafi Shajakhan
2012-06-07 6:15 ` Sujith Manoharan
2012-06-07 6:27 ` Mohammed Shafi Shajakhan
2012-06-07 6:25 ` Joe Perches
2012-06-07 7:11 ` Mohammed Shafi Shajakhan
2012-06-07 7:24 ` Joe Perches
2012-06-07 7:37 ` Mohammed Shafi Shajakhan
2012-06-07 7:57 ` Joe Perches
2012-06-07 8:38 ` Mohammed Shafi Shajakhan
2012-06-07 19:52 ` Joe Perches
2012-06-13 4:59 ` Mohammed Shafi Shajakhan [this message]
2012-06-14 1:13 ` Joe Perches
2012-06-14 4:37 ` Mohammed Shafi Shajakhan
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=4FD81E2C.1000507@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).