From: Dan Williams <dcbw@redhat.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: libertas and endianness
Date: Mon, 08 Oct 2007 08:55:20 -0400 [thread overview]
Message-ID: <1191848120.2703.16.camel@localhost.localdomain> (raw)
In-Reply-To: <200710081106.06475.hs4233@mail.mn-solutions.de>
On Mon, 2007-10-08 at 11:06 +0200, Holger Schurig wrote:
> > I.e. it tries to store 0x0100 resp. 0x0200 into keytype[i],
> > which is is u8.
> >
> > Gr{oetje,eeting}s,
>
> Dan Williams partially fixed this on 2nd August. Seems that
> libertas patches needs ages to trickle upwards.
The patches are queued for 2.6.24 and are already in net-2.6.24.
They've been in net-2.6.24 for quite a while. Anything that's in
libertas-2.6 is already queued for 2.6.24 when the merge window opens.
http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.24.git;a=commit;h=1118759a15da6e97e8101a7f025b2947f190505f
The order is:
libertas-2.6 -> wireless-2.6 -> net-2.6.x -> linus
So these will go upstream. Where these patches _could_ go is to stable,
for fixing up what's already out there in 2.6.22 and 2.6.23.
Dan
> The patch is buried in the libertas-2.6 tree, in the
> branch "libertas". See here:
>
> http://git.infradead.org/?p=libertas-2.6.git;a=commitdiff;h=1bf710a1f1bd816897be3b0441d3c916ea1b9ab9
>
>
>
> However, in my next mail I'm attaching a cosmetic change for
> this. There's no need to define a constant for an u8 as 0x0001
> and 0x0002 ...
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-10-08 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 10:15 libertas and endianness Geert Uytterhoeven
2007-10-08 9:06 ` Holger Schurig
2007-10-08 12:55 ` Dan Williams [this message]
2007-10-08 9:07 ` [PATCH] libertas: fix u8 constant Holger Schurig
2007-10-08 12:55 ` Dan Williams
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=1191848120.2703.16.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=linux-wireless@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