netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Pavel Machek <pavel@ucw.cz>
Cc: netdev@oss.sgi.com, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ipw2100 wireless driver
Date: Wed, 14 Jul 2004 15:15:23 +0200	[thread overview]
Message-ID: <20040714131523.GA498@ucw.cz> (raw)
In-Reply-To: <20040714114135.GA25175@elf.ucw.cz>

On Wed, Jul 14, 2004 at 01:41:35PM +0200, Pavel Machek wrote:
> Hi!
> 
> What is the status of ipw2100? Is there chance that it would be pushed
> into mainline?
> 
> I have few problems with that:
> 
> * it will not compile with gcc-2.95. Attached patch fixes one problem
> but more remain.

Wouldn't "struct sk_buff **fragments" be a more correct fix?

> --- ipw2100-ofic/ieee80211.h	2004-07-09 06:32:17.000000000 +0200
> +++ ipw2100-0.49/ieee80211.h	2004-07-14 13:18:50.000000000 +0200
> @@ -440,7 +440,7 @@
>  	u16 reserved;
>  	u16 frag_size;
>  	u16 payload_size;
> -	struct sk_buff *fragments[];
> +	struct sk_buff *fragments[1];
>  };
>  
>  extern struct ieee80211_txb *ieee80211_skb_to_txb(struct ieee80211_device *ieee, 
> 
> * it requires CONFIG_CRYPTO, but fails to force it in Kconfig.
> 
> 									Pavel
> -- 
> People were complaining that M$ turns users into beta-testers...
> ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  parent reply	other threads:[~2004-07-14 13:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 11:41 ipw2100 wireless driver Pavel Machek
2004-07-14 11:48 ` Jeff Chua
2004-07-14 11:55   ` Pavel Machek
2004-08-09 20:15     ` Tomas Szepe
2004-08-10  5:02       ` Jeff Chua
2004-08-10  6:55         ` Christoph Hellwig
2004-08-10 10:16           ` Pavel Machek
2004-08-10 10:34             ` Christoph Hellwig
2004-08-11 12:17               ` Pavel Machek
2004-08-11 17:54                 ` Jeff Garzik
2004-08-11 20:27                   ` Pavel Machek
2004-08-11 22:01                     ` Jeff Garzik
2004-08-11 10:16             ` James Ketrenos
2004-08-11 10:44               ` Christoph Hellwig
2004-08-11 10:53                 ` Wichert Akkerman
2004-08-11 10:59                   ` Christoph Hellwig
2004-08-11 16:21                 ` James Ketrenos
2004-08-11 16:30                   ` Stephen Hemminger
2004-08-11 16:33                     ` Tomas Szepe
2004-08-11 16:51                       ` Christoph Hellwig
2004-08-11 17:02                         ` Tomas Szepe
2004-08-11 17:11                           ` Christoph Hellwig
2004-08-11 17:22                             ` Tomas Szepe
2004-08-11 18:55                           ` John Stoffel
2004-08-11 23:55                       ` Jeff Chua
2004-08-12  3:47                   ` Luis R. Rodriguez
2004-08-11 17:51               ` Jeff Garzik
2004-07-14 12:30   ` Tomas Szepe
2004-07-14 12:27 ` Pavel Machek
2004-07-14 13:15 ` Vojtech Pavlik [this message]
2004-07-14 13:42   ` Pavel Machek

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=20040714131523.GA498@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=pavel@ucw.cz \
    /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).