linux-kernel - Re: [PATCH EDAC v26 00/66] EDAC patches for v3.5

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 18 May 2012 19:53:36 +0200
From:	Borislav Petkov <bp@...64.org>
To:	Mauro Carvalho Chehab <mchehab@...hat.com>
Cc:	Borislav Petkov <bp@...64.org>,
	Linux Edac Mailing List <linux-edac@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH EDAC v26 00/66] EDAC patches for v3.5

On Fri, May 18, 2012 at 02:43:04PM -0300, Mauro Carvalho Chehab wrote:
> >>   RAS: Add a tracepoint for reporting memory controller events
> > 
> > Are you kidding me?
> > 
> > You want to send patches upstream which are still in review and 
>
> No, I want to post the last version of the patches and provide a
> clearer description of what this patch series do, before sending the
> git pull request when the merge window opens.

I'm fine with offloading some of your stuff which has been reviewed
and agreed upon but pushing in stuff into the merge window (it should
open over the weekend, my clairvoyant skills tell me) which is still in
review is a no-no.

You also know about the linux-next rule, right? Now you can't tell me
your patches have been for a couple of weeks in linux-next because
you're constantly rebasing them.

So pls drop the act and adhere to the rules like everyone else.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
--
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/