From: Ivo van Doorn <ivdoorn@gmail.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: rt2400-devel@lists.sourceforge.net, Jiri Benc <jbenc@suse.cz>,
netdev@vger.kernel.org, John Linville <linville@tuxdriver.com>
Subject: Re: [Rt2400-devel] [PATCH] rt2x00: Fix compilation for d80211 hwmode API change
Date: Fri, 15 Dec 2006 20:52:38 +0100 [thread overview]
Message-ID: <200612152052.39187.IvDoorn@gmail.com> (raw)
In-Reply-To: <200612152042.21076.mb@bu3sch.de>
Hi,
> This fixes compilation for the d80211 hwmode API change.
I haven't had time yet to look closely at more of the benefits
of the new hwmode API change, but this patch looks good.
Thanks!
> Signed-off-by: Michael Buesch <mb@bu3sch.de>
Signed-off-by: Ivo van Doorn <IvDoorn@gmail.com>
prev parent reply other threads:[~2006-12-15 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 19:42 [PATCH] rt2x00: Fix compilation for d80211 hwmode API change Michael Buesch
2006-12-15 19:52 ` Ivo van Doorn [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=200612152052.39187.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=rt2400-devel@lists.sourceforge.net \
/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).