From: Johannes Berg <johannes@sipsolutions.net>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: fixing the warning storm for budding chipsets without ampdu_action defined
Date: Wed, 05 Dec 2012 10:17:52 +0100 [thread overview]
Message-ID: <1354699072.9972.7.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CABPxzYKrYPo9S-t6dSPS3qgwKcsaD=uoiAm2+naS7C6D=3KBOg@mail.gmail.com> (sfid-20121205_101332_218158_7832CE9D)
On Wed, 2012-12-05 at 14:43 +0530, Krishna Chaitanya wrote:
> Warn once should suffice.
Indeed :)
> Eg: our driver doesn't support the ampdu_action yet, so
> seeing a lot of warnings, hence the check for any
> new drivers to avoid messing the kernel log.
Please make the subject active voice ("fix the warning storm [...]").
Your patches are all whitespace damaged.
$ git am -s /tmp/\[PATCH\]_mac80211\:_fixing_the_warning_storm_for_budding_chipsets_without_ampdu_action_defined.mbox
Applying: mac80211: fixing the warning storm for budding chipsets without ampdu_action defined
fatal: corrupt patch at line 10
Patch failed at 0001 mac80211: fixing the warning storm for budding chipsets without ampdu_action defined
The copy of the patch that failed is found in:
/home/johannes/sys/wireless/.git/rebase-apply/patch
When you have resolved this problem, run "git am --resolved".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
johannes
next prev parent reply other threads:[~2012-12-05 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 9:13 [PATCH] mac80211: fixing the warning storm for budding chipsets without ampdu_action defined Krishna Chaitanya
2012-12-05 9:17 ` Johannes Berg [this message]
2012-12-05 11:07 ` Krishna Chaitanya
2012-12-05 11:42 ` Johannes Berg
2012-12-05 14:04 ` Seth Forshee
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=1354699072.9972.7.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chaitanya.mgit@gmail.com \
--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 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).