From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "David S. Miller" <davem@redhat.com>
Cc: netdev@oss.sgi.com
Subject: Re: PATCH: [SKBUFF] Introduce skb_set_link_header_offset(skb, offset)
Date: Tue, 05 Oct 2004 18:25:09 -0300 [thread overview]
Message-ID: <41631135.5040609@conectiva.com.br> (raw)
In-Reply-To: <20041005135338.6f381fa1.davem@redhat.com>
David S. Miller wrote:
> On Tue, 05 Oct 2004 17:09:08 -0300
> Arnaldo Carvalho de Melo <acme@conectiva.com.br> wrote:
>
>
>>Hi David,
>>
>> Please consider pulling from:
>>
>>bk://kernel.bkbits.net/acme/sk_buff-2.4
>>
>> Now there are 14 outstanding changesets in this tree.
>
>
> Slow down. :-)
Oh, flow control! :-)
>
> There are bugs in your earlier changesets which are going
> to make it hard for me to pull this tree in. Let's work
> one or two changesets at a time, not 14 ok? :-)
>
> First bug, in ChangeSet 1.2032, drivers/net/wireless/orinoco.c
>
> You change "skb->mac.raw + ETH_ALEN" into
> "eth_hdr(skb)->h_source". That can't be right
> since orinoco_spy_gather() expects a pointer for
> that argument.
>
> Same error in the drivers/net/wireless/wavelan.c change
> in ChangeSet 1.2032, replacing skb->mac.raw (a pointer)
> with eth_hdr(skb)->h_dest in the call to wv_packet_info.
humm, puzzled, isn't eth_hdr(skb)->h_dest a pointer of the
same tipe (unsigned char *), that points to same place as
skb->mac.raw? :-)
But perhaps the guy wanted the whole link header, I got
confused because afterwards it uses the ETH_ALEN offset,
meaning that it wanted now the second struct ethhdr field,
lemme look again at this code...
Nope, you're right, seems to be the 802.11 three adresses stuff,
done in an ad-hoc confusing way, my mistake.
> Please start to submit this stuff in smaller pieces and
> fix the above bugs, thanks.
mmkay sir!
Best Regards,
- Arnaldo
prev parent reply other threads:[~2004-10-05 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 20:09 PATCH: [SKBUFF] Introduce skb_set_link_header_offset(skb, offset) Arnaldo Carvalho de Melo
2004-10-05 20:53 ` David S. Miller
2004-10-05 21:25 ` Arnaldo Carvalho de Melo [this message]
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=41631135.5040609@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=davem@redhat.com \
--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 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).