From: Jiri Benc <jbenc@suse.cz>
To: Michael Wu <flamingice@sourmilk.net>
Cc: linux-wireless@vger.kernel.org, John Linville <linville@tuxdriver.com>
Subject: Re: "Stable" branch of mac80211
Date: Sun, 29 Apr 2007 21:55:28 +0200 [thread overview]
Message-ID: <20070429215528.02c51cf9@logostar.upir.cz> (raw)
In-Reply-To: <200704291414.19963.flamingice@sourmilk.net>
On Sun, 29 Apr 2007 14:14:14 -0400, Michael Wu wrote:
> wireless-dev has been updated recently. One of the conflicts can be resolved
> easily. There's also an API change which conflicts with the qdisc fixes
> because tcf_destroy is no longer exported. A patch for that is attached.
I folded the patch into the qdisc fix patch and rebased my tree (all
branches).
I also ensured the previously misapplied radiotap patch is now applied
correctly and dropped the "move radiotap removal code to right function"
patch.
Thanks,
Jiri
--
Jiri Benc
SUSE Labs
next prev parent reply other threads:[~2007-04-29 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-29 17:48 "Stable" branch of mac80211 Jiri Benc
2007-04-29 18:14 ` Michael Wu
2007-04-29 19:55 ` Jiri Benc [this message]
2007-04-30 16:52 ` James Ketrenos
2007-04-30 17:29 ` Jiri Benc
2007-04-30 18:45 ` John W. Linville
2007-05-01 1:00 ` Jiri Benc
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=20070429215528.02c51cf9@logostar.upir.cz \
--to=jbenc@suse.cz \
--cc=flamingice@sourmilk.net \
--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