From: Stanislav Fomichev <kernel@fomichev.me>
To: Greg KH <greg@kroah.com>
Cc: brudley@broadcom.com, gregkh@suse.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] brcm80211: remove multiple calls to wl_release_fw
Date: Sat, 19 Feb 2011 12:03:49 +0300 [thread overview]
Message-ID: <4d5f877a.1211cc0a.3680.ffffabbc@mx.google.com> (raw)
In-Reply-To: <20110218205700.GC796@kroah.com>
> This doesn't apply on linux-next, what tree is it supposed to be for?
I suppose it was based on the Linus's tree (I didn't know that the
developing is going on on this list).
Anyway, pls drop this patch; the similar fixes should be done in one of
the Roland Vossen's patches.
--
Stas
prev parent reply other threads:[~2011-02-19 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-12 15:00 [PATCH] brcm80211: remove multiple calls to wl_release_fw Stanislav Fomichev
2011-02-14 19:59 ` Roland Vossen
2011-02-14 20:22 ` Dan Carpenter
2011-02-14 20:40 ` Roland Vossen
2011-02-14 21:03 ` Stanislav Fomichev
2011-02-14 21:07 ` Stanislav Fomichev
2011-02-14 21:20 ` Dan Carpenter
2011-02-18 20:57 ` Greg KH
2011-02-19 9:03 ` Stanislav Fomichev [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=4d5f877a.1211cc0a.3680.ffffabbc@mx.google.com \
--to=kernel@fomichev.me \
--cc=brudley@broadcom.com \
--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 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).