linux-kernel - Re: [git pull] drm gma500 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 17 Jul 2012 07:09:09 +1000
From:	Dave Airlie <airlied@...il.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Dave Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org,
	DRI mailing list <dri-devel@...ts.freedesktop.org>
Subject: Re: [git pull] drm gma500 fixes

On Tue, Jul 17, 2012 at 7:07 AM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> On Mon, 16 Jul 2012 13:44:32 -0700
> Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>
>> On Mon, Jul 16, 2012 at 12:42 PM, Dave Airlie <airlied@...ux.ie> wrote:
>> >
>> > Sorry been travelling and a bit neglectful of some of Alan's
>> > patches,
>>
>> I actually took the three Alan sent me already, exactly because they
>> seemed harmless and I didn't know your schedule.
>>
>> Your pull has a "gma500: Fix frequency detection" patch that I haven't
>> seen though, which makes me wonder if Alan wants that one too. He only
>> sent me a series of the three other patches..
>>
>> Alan?
>
> The frequency detect bug isn't a regression, indeed its not clear it's a
> path ever taken.

Cool then drop it, I just found it in my INBOX,

anyways I also sent a dodgy URL in the pull, since I wasn't on my
usual machine I hadn't updated stuff.

So yeah ignore this one and I'll add the extra patch into -next.

Thanks,
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/