All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Ketrenos <jketreno@linux.jf.intel.com>
To: jt@hpl.hp.com
Cc: Andrew Morton <akpm@osdl.org>, Joshua Kwan <jkwan@rackable.com>,
	linux-kernel@vger.kernel.org
Subject: Re: What happened to linux/802_11.h?
Date: Tue, 22 Jun 2004 20:39:44 -0500	[thread overview]
Message-ID: <40D8DF60.1090803@linux.jf.intel.com> (raw)
In-Reply-To: <20040622004813.GA12334@bougret.hpl.hp.com>

Jean Tourrilhes wrote:

>On Mon, Jun 21, 2004 at 05:38:27PM -0700, Andrew Morton wrote:
>  
>
>>Joshua Kwan <jkwan@rackable.com> wrote:
>>    
>>
>>>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
>  
>
This is the path I was planning to take when I read about 802_11.h 
possibly going away a while ago.  The file finally going away will just 
raise the priority of that effort a bit :)  Changing the code to use the 
headers in drivers/net/wireless isn't a big task -- I'll put the change 
into the next snapshot of ipw2100.

Thanks,
James
(of ipw2100.sf.net)

  reply	other threads:[~2004-06-23  1:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21 22:26 What happened to linux/802_11.h? Joshua Kwan
2004-06-22  0:38 ` Andrew Morton
2004-06-22  0:48   ` Jean Tourrilhes
2004-06-23  1:39     ` James Ketrenos [this message]
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=40D8DF60.1090803@linux.jf.intel.com \
    --to=jketreno@linux.jf.intel.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 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.