linux-kernel - Re: [GIT] floppy

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]

Message-ID: <CA+1xoqdwZHH=VMKvddr8bhceQHz+F5Xm5rgwJACUcnH+-uQjdg@mail.gmail.com>
Date:	Wed, 7 Nov 2012 16:58:33 -0500
From:	Sasha Levin <levinsasha928@...il.com>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Jens Axboe <axboe@...nel.dk>, linux-kernel@...r.kernel.org
Subject: Re: [GIT] floppy

On Wed, Nov 7, 2012 at 3:48 PM, Jiri Kosina <jkosina@...e.cz> wrote:
> On Wed, 7 Nov 2012, Sasha Levin wrote:
>
>> Hi guys!
>>
>> This is me complaining that I still see the spews that this pull
>> request should fix, probably because this mail got lost.
>
> You are seeing that on -next, right?

Yup.

> That's because a different version of the patchset has been pushed to
> Linus, but for-next branch in Jens' tree still contains the old patchset
> containing the faulty patch (which is never going upstream).
>
> The fixed series is now in Linus' tree (as per -rc4), and I guess you are
> not having the problem there, right?

I haven't thought of trying just Linus's tree because I thought that
the original patch
that causes the breakage didn't make it there, so it would be obvious
that it would
work fine.

I'll give it a go I guess.


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