From: "Franky Lin" <frankyl@broadcom.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] brcm80211: remove some truely barftastic code
Date: Thu, 11 Oct 2012 09:33:58 -0700 [thread overview]
Message-ID: <5076F4F6.70103@broadcom.com> (raw)
In-Reply-To: <20121011162505.2643.87138.stgit@bob.linux.org.uk>
On 10/11/2012 09:25 AM, Alan Cox wrote:
> From: Alan Cox <alan@linux.intel.com>
>
> It's not used or called but please make it go away before someone copies or
> uses it
>
> Signed-off-by: Alan "minus lunch" Cox <alan@linux.intel.com>
Indeed this should go away. Thanks!
Acked-by: Franky Lin <frankyl@broadcom.com>
prev parent reply other threads:[~2012-10-11 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 16:25 [PATCH 1/2] brcm80211: remove some truely barftastic code Alan Cox
2012-10-11 16:25 ` [PATCH 2/2] ath9k: Fix broken conditional Alan Cox
2012-10-12 4:59 ` Mohammed Shafi
2012-10-11 16:33 ` Franky Lin [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=5076F4F6.70103@broadcom.com \
--to=frankyl@broadcom.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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).