From: CaT <cat@zip.com.au>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
bzolnier@gmail.com, stable@kernel.org, ben@decadent.org.uk,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.34 (rt2860 regression)
Date: Tue, 18 May 2010 23:17:06 +1000 [thread overview]
Message-ID: <20100518131706.GZ2657@zip.com.au> (raw)
In-Reply-To: <20100518125539.GA23181@kroah.com>
On Tue, May 18, 2010 at 05:55:39AM -0700, Greg KH wrote:
> I do not understand. The firmware is now part of the linux-firmware
> tree, and if you install that, it is working just fine, right? We moved
> the firmware out of the kernel tree on purpose.
>
> So what is the problem here?
Well, the driver used to work and appears to be useless without it. I guess
I'm wondering why it was kept out of the firmware directory where all the
other firmware lives (and so allow the driver to simply continue to work
and allow it to be compiled in).
At the moment all the change appears to have done is break things that have
been working without issue since before the driver was even in staging.
--
"A search of his car uncovered pornography, a homemade sex aid, women's
stockings and a Jack Russell terrier."
- http://www.news.com.au/story/0%2C27574%2C24675808-421%2C00.html
next prev parent reply other threads:[~2010-05-18 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 21:39 Linux 2.6.34 Linus Torvalds
2010-05-17 3:00 ` Bill Davidsen
2010-05-18 11:44 ` Linux 2.6.34 (rt2860 regression) CaT
2010-05-18 12:55 ` Greg KH
2010-05-18 13:17 ` CaT [this message]
2010-05-18 13:33 ` Greg KH
2010-05-18 14:13 ` CaT
2010-05-18 14:43 ` Greg KH
2010-05-18 15:06 ` Nick Bowler
2010-05-18 16:59 ` Bill Davidsen
2010-05-18 18:37 ` Ben Hutchings
2010-05-18 20:13 ` Greg KH
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=20100518131706.GZ2657@zip.com.au \
--to=cat@zip.com.au \
--cc=ben@decadent.org.uk \
--cc=bzolnier@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.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.