From: Larry Finger <Larry.Finger@lwfinger.net>
To: Peter Wu <lekensteyn@gmail.com>
Cc: Chaoming_Li <chaoming_li@realsil.com.cn>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
John W Linville <linville@tuxdriver.com>
Subject: Re: [PATCH 3/3] rtlwifi: remove unused allow_all_destaddr functions
Date: Fri, 14 Feb 2014 15:57:40 -0600 [thread overview]
Message-ID: <52FE9154.30007@lwfinger.net> (raw)
In-Reply-To: <5255317.CRdrWcWANY@al>
On 02/14/2014 03:48 PM, Peter Wu wrote:
> On Friday 14 February 2014 15:38:32 Larry Finger wrote:
>> On 02/14/2014 12:03 PM, Peter Wu wrote:
>>> Unused as configure_filter takes care of setting/clearing RCR_AAP.
>>>
>>> Signed-off-by: Peter Wu <lekensteyn@gmail.com>
>>
>> NACK - at least for now. This patch has merge conflicts for the set of
>> patches that add the rtl8723be driver, and would cause build errors if the
>> merge were fixed. I will hang on to it and apply it later when the
>> rtl8723be merge is done.
>
> Fair enough, the next patch will strip even more then :-)
No harm in sending more as [RFC/RFT] items. That way they will get reviewed, and
I will be able to test them. Once the conflicts are cleared, then I can push
them to John with a "From" you.
Larry
prev parent reply other threads:[~2014-02-14 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 18:03 [PATCH 0/3] rtlwifi promiscious mode fix and cleanup Peter Wu
2014-02-14 18:03 ` [PATCH 1/3] rtlwifi: avoid accessing RCR directly Peter Wu
2014-02-14 21:28 ` Larry Finger
2014-02-14 21:46 ` Peter Wu
2014-02-14 18:03 ` [PATCH 2/3] rtlwifi: properly apply filter flags Peter Wu
2014-02-14 21:32 ` Larry Finger
2014-02-14 18:03 ` [PATCH 3/3] rtlwifi: remove unused allow_all_destaddr functions Peter Wu
2014-02-14 21:38 ` Larry Finger
2014-02-14 21:48 ` Peter Wu
2014-02-14 21:57 ` Larry Finger [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=52FE9154.30007@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=lekensteyn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).