From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Joshua Kwan <jkwan@rackable.com>, linux-kernel@vger.kernel.org
Subject: Re: What happened to linux/802_11.h?
Date: Mon, 21 Jun 2004 17:48:13 -0700 [thread overview]
Message-ID: <20040622004813.GA12334@bougret.hpl.hp.com> (raw)
In-Reply-To: <20040621173827.0403618b.akpm@osdl.org>
On Mon, Jun 21, 2004 at 05:38:27PM -0700, Andrew Morton wrote:
> Joshua Kwan <jkwan@rackable.com> wrote:
> >
> > Hello,
> >
> > linus.patch from -mm1:
> > # BitKeeper/deleted/.del-802_11.h~9b6bd4cff8af7a90
> > # 2004/06/18 09:47:58-07:00 torvalds@ppc970.osdl.org +0 -0
> > # Delete: include/linux/802_11.h
> >
> > Why was this file removed?
>
> Nothing in the kernel is using it.
It was a remnant from the old aironet4500 driver that was
removed during 2.5.X. It was also confusing because there is a file
called drivers/net/wireless/ieee802_11.h that has a somewhat similar
purpose and is used in various drivers (Orinoco, Atmel). I think it
was discussed on netdev.
I was not aware that IPW2100 was using it. I could not try
this driver because it doesn't compile with gcc 2.95.
> > The IPW2100 driver
> > (http://ipw2100.sourceforge.net) uses its definitions and now won't build
> > against -bk or -mm kernel source.
>
> Jean, should we restore 802_11.h, or is there some alternative file which
> that driver should be using?
Well, Jeff explicitely said that we should not care about
drivers outside the kernel ;-)
Seriously, I see three solutions :
1) Convert ipw2100 to using drivers/net/wireless/ieee802_11.h,
extend this header as necessary
2) Have ipw2100 use a private version of 802_11.h
3) Convince us that this file is really needed (good luck)
Obviously (1) is better in the long term.
Have fun...
Jean
next prev parent reply other threads:[~2004-06-22 0:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 22:26 Joshua Kwan
2004-06-22 0:38 ` Andrew Morton
2004-06-22 0:48 ` Jean Tourrilhes [this message]
2004-06-23 1:39 ` James Ketrenos
2004-06-23 16:16 ` Jean Tourrilhes
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=20040622004813.GA12334@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=akpm@osdl.org \
--cc=jkwan@rackable.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®