From: Hin-Tak Leung <htl10@users.sourceforge.net>
To: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Cc: herton@mandriva.com.br, Larry.Finger@lwfinger.net,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] rtl8187: use SET_IEEE80211_PERM_ADDR
Date: Tue, 4 May 2010 21:33:05 +0000 (GMT) [thread overview]
Message-ID: <28272.18599.qm@web23107.mail.ird.yahoo.com> (raw)
In-Reply-To: <1273002809-8595-1-git-send-email-linville@tuxdriver.com>
--- On Tue, 4/5/10, John W. Linville <linville@tuxdriver.com> wrote:
> Signed-off-by: John W. Linville
> <linville@tuxdriver.com>
Acked-by: Hin-Tak Leung <htl10@users.sourceforge.net>
Look likes a good direction of change to hide the wiphy details.
Hin-Tak
prev parent reply other threads:[~2010-05-04 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 19:53 [PATCH] rtl8187: use SET_IEEE80211_PERM_ADDR John W. Linville
2010-05-04 21:33 ` Hin-Tak Leung [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=28272.18599.qm@web23107.mail.ird.yahoo.com \
--to=htl10@users.sourceforge.net \
--cc=Larry.Finger@lwfinger.net \
--cc=herton@mandriva.com.br \
--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).