linux-kernel - Re: [GIT PULL] EDAC updates for 4.

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]

Date:	Wed, 24 Jun 2015 14:30:48 +0200
From:	Borislav Petkov <bp@...e.de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-edac <linux-edac@...r.kernel.org>,
	the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [GIT PULL] EDAC updates for 4.

On Wed, Jun 24, 2015 at 05:14:34AM -0700, Linus Torvalds wrote:
> This shows such a fundamental misunderstanding of what you should send
> me that in starting to doubt all your other pull requests. How many of
> them worked by our luck? If you are not testing what you actually send
> me, I simply don't want to pull from you. It's that simple.

Ok, now this is really uncalled for.

I made the mistake of having the RAS x86 stuff going through tip - as it
always does - and have the drivers/edac/ changes in the EDAC tree.

But I have always merged the tip/x86/ras branch which contained the x86
changes into the EDAC tree when testing. Basically what I should've done
with the pull request too.

And dammit, I did test the hell of this thing. Like everything else I'm
testing. I'm trying to do my best but I can only try.

If there's anything I can do to stop you from doubting my pull requests,
please let me know.

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
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/