03.03.2010 01:02, Dave Airlie skrev:
>>> x86 after PPC (I think I just validated Ingo).
>>
>> Why is VGA_SWITCHEROO enabled by default?
>
> because it does nothing on anything except the laptops in question and on
> those it does nothing except add a control file in debugfs?
>
> So how am I suppose
On Wed, 3 Mar 2010, Dave Airlie wrote:
>
> So can we get linux-next builds to build with *your* Kconfig? This should
> cut down the amount of crap you see considerably.
No.
Dave, _think_ about what you're saying.
The absolute last thing we want to do is to make it easier for crap to
flow thr
0/3/3 Dave Airlie :
>>
>> Never mind. I've unpulled the whole effin' mess since it doesn't even
>> compile:
>>
>> drivers/gpu/drm/nouveau/nouveau_acpi.c:191: error: redefinition of
>> ‘nouveau_register_dsm_handler’
>> drivers/gpu/drm/nouveau/nouveau_drv.h:859: note: previous definition
On Wed, Mar 3, 2010 at 9:40 AM, Linus Torvalds
wrote:
>
>
> On Wed, 3 Mar 2010, Dave Airlie wrote:
>>
>> Did I mention that driver is in STAGING?
>
> Staging is for _improving_ the quality of the drivers, not for making it
> worse.
>
> We still very much have quality standards. The staging tree is
On Wed, 3 Mar 2010, Dave Airlie wrote:
>
> Did I mention that driver is in STAGING?
Staging is for _improving_ the quality of the drivers, not for making it
worse.
We still very much have quality standards. The staging tree is for things
to get in that don't quite _reach_ the standards we exp
> > x86 after PPC (I think I just validated Ingo).
>
> Why is VGA_SWITCHEROO enabled by default?
because it does nothing on anything except the laptops in question and on
those it does nothing except add a control file in debugfs?
So how am I supposed to indicate to distro vendors that somethin
>
> Never mind. I've unpulled the whole effin' mess since it doesn't even
> compile:
>
> drivers/gpu/drm/nouveau/nouveau_acpi.c:191: error: redefinition of
> ‘nouveau_register_dsm_handler’
> drivers/gpu/drm/nouveau/nouveau_drv.h:859: note: previous definition of
> ‘nouveau_register
On Tue, 2 Mar 2010, Linus Torvalds wrote:
>
> It's still code. And if the user didn't ask for it, it should damn well
> not be there.
And I repeat: unless the feature cures cancer, it's not on by default.
Sometimes we split up _old_ features as config options, or do things that
are meant to
On Mon, 1 Mar 2010, Dave Airlie wrote:
>
> Same tree as yesterday with a warning + PPC build fix + fix for build on
> x86 after PPC (I think I just validated Ingo).
Why is VGA_SWITCHEROO enabled by default?
We don't do things like that. New drivers and new features are _not_
enabled by defau
On Tue, 2 Mar 2010, Dave Airlie wrote:
>
> because it does nothing on anything except the laptops in question and on
> those it does nothing except add a control file in debugfs?
It's still code. And if the user didn't ask for it, it should damn well
not be there.
> So how am I supposed to i
On Tue, 2 Mar 2010, Linus Torvalds wrote:
>
> I disabled it in the merge, since I had to fix up that file anyway. But
> please don't make me do these so-called "evil merges" where I end up
> modifying the thing I merge.
Never mind. I've unpulled the whole effin' mess since it doesn't even
co
Same tree as yesterday with a warning + PPC build fix + fix for build on
x86 after PPC (I think I just validated Ingo).
The following changes since commit 60b341b778cc2929df16c0a504c91621b3c6a4ad:
Linus Torvalds (1):
Linux 2.6.33
are available in the git repository at:
ssh://master
12 matches
Mail list logo
