From: Chr <chunkeey@web.de>
To: Dan Williams <dcbw@redhat.com>
Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
linux-wireless@vger.kernel.org
Subject: Re: prism54 stopped working after upgrade from kernel 2.6.25.14-69.fc8 to 2.6.26.3-14.fc8
Date: Mon, 22 Sep 2008 23:59:40 +0200 [thread overview]
Message-ID: <200809222359.40354.chunkeey@web.de> (raw)
In-Reply-To: <1221947069.11865.11.camel@localhost.localdomain>
On Saturday 20 September 2008 23:44:29 Dan Williams wrote:
> On Mon, 2008-09-22 at 23:32 +0200, Chr wrote:
> > > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=co
> > > >mmit ;h=aaa1553512b9105699113ea7e2ea726f3d9d4de2
> > >
> > > Is that commit not in stable 2.6.26 yet or something?
> >
> > Hmm, no? AFAIK The mac80211 multiqueue changes went in somewhere in the
> > 2.6.27-rc cycle. so 2.6.26.stable doesn't need any extra patches, right?
>
> Ah yeah right; I guess I don't understand the link you posted then. I'd
> thought it was something like "you need this patch which Fedora doesn't
> have in their kernel".
Hmm? I though fedora backported multiqueue back into their 2.6.26?
Atleast, the original (but with a buggy p54) multiqueue patch seems to be in
the linux-wirless-2.6-pending.diff/patch file... but this fix is nowhere to
be found inside fedora's kernel source?
So, Dan? can you add that patch to the next fedora's 2.6.26 kernel release?
Regards,
Chr
next prev parent reply other threads:[~2008-09-22 21:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 18:38 prism54 stopped working after upgrade from kernel 2.6.25.14-69.fc8 to 2.6.26.3-14.fc8 Philippe Waroquiers
2008-09-22 18:42 ` Luis R. Rodriguez
2008-09-22 19:22 ` Philippe Waroquiers
2008-09-22 20:05 ` Chr
2008-09-20 21:08 ` Dan Williams
2008-09-22 21:32 ` Chr
2008-09-20 21:44 ` Dan Williams
2008-09-22 21:59 ` Chr [this message]
2008-09-22 22:13 ` John W. Linville
2008-09-23 17:30 ` Kyle McMartin
2008-10-03 19:37 ` Philippe Waroquiers
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=200809222359.40354.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=dcbw@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=philippe.waroquiers@skynet.be \
/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).