linux-kernel - Re: [git pull] drm fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTinDSMqlwOsNfX-K2vDN9HeQL19mtXEDAp8mqVjz@mail.gmail.com>
Date:	Tue, 8 Jun 2010 06:41:40 +1000
From:	Dave Airlie <airlied@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Dave Airlie <airlied@...ux.ie>, dri-devel@...ts.freedesktop.org,
	linux-kernel@...r.kernel.org
Subject: Re: [git pull] drm fixes

On Tue, Jun 8, 2010 at 6:26 AM, Dave Airlie <airlied@...il.com> wrote:
> On Tue, Jun 8, 2010 at 4:00 AM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
>>
>>
>> On Mon, 7 Jun 2010, Dave Airlie wrote:
>>>
>>> 3 regressions fixes, one radeon loading on IGP, one i865 loading, one and
>>> an evergreen userspace interaction workaround.
>>
>> This is:
>>
>>         26 files changed, 372 insertions(+), 66 deletions(-)
>>
>> and there are apparently several reports of known problems (the problem
>> with modesetting) that isn't even addressed.
>
> Okay, not sure what the addressed regression you are talking about, do
> you want  regression fixes early like you always say or do you want to
> wait until I have every regression reported fixes before I send a pull
> request?

Oh the one where I said to the reporter, I've reproduced this, and
will fix it tomorrow when I have proper time and access to my test
machine?

I didn't think writing a fix in the 5 mins before I left the test
machine and sending it you was acceptable, again can you maintain some
semblance of consistency across maintainers/releases?

Like I'm happy if you really enforce this no features idea, I'd be
really happy if you did it every release since it makes it a lot
easier to push back to submaintainers if you can point at Linus not
pulling features from people. However its really hard to push back on
submaintainers and one of the reasons Eric talks to you direct after
rc1, when you can be very inconsistent about what you pull and from
whom. Like I can tell someone this isn't going in this release, then
you'll pull something uglier  from someone else in -rc3 and I end up
looking like stupid because I said there was no hope of getting
anything in. Consistency is something that would make everyone's life
easier, across all releases and all maintainers.

Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/