From: Pavel Roskin <proski@gnu.org>
To: Dan Williams <dcbw@redhat.com>
Cc: netdev@oss.sgi.com, hermes@gibson.dropbear.id.au
Subject: Re: orinoco upstream merge to kernel status?
Date: Tue, 29 Mar 2005 11:46:44 -0500 [thread overview]
Message-ID: <1112114804.29524.8.camel@dv> (raw)
In-Reply-To: <1112110149.16060.13.camel@dcbw.boston.redhat.com>
On Tue, 2005-03-29 at 10:29 -0500, Dan Williams wrote:
> Hi,
>
> I've just looked over the diff between current 2.6.12rc1 and upstream
> "for_linus" branch of the orinoco drivers. I found that the delta is
> almost 100% due to monitor mode/scanning code that's found in the
> upstream driver. That's the last _important_ piece that has to get
> merged to the mainline kernel. It seems all the other trivial pieces
> have been merged already.
>
> David/Pavel: is it correct that the only bits left are monitor
> mode/scanning, and that they cannot be separated? Should that diff just
> be posted as a patch to netdev? Or are there other issues with the
> "for_linus" branch right now that prevent the final merge from
> occurring?
>
Hi, Dan!
The remaining differences are only in orinoco.c and orinoco.h. However,
it's more than just monitor mode and scanning. The driver in 2.6.12-rc1
is basically version 0.14alpha2, and there have been more changes since
then. For example, support for joining a specific access point.
David submitted previous changes. I can submit the rest if David hasn't
done it. David?
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2005-03-29 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 15:29 orinoco upstream merge to kernel status? Dan Williams
2005-03-29 16:46 ` Pavel Roskin [this message]
2005-03-30 1:04 ` David Gibson
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=1112114804.29524.8.camel@dv \
--to=proski@gnu.org \
--cc=dcbw@redhat.com \
--cc=hermes@gibson.dropbear.id.au \
--cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.