linux-kernel - Re: [PATCH v.23-2] RAS: use tracepoint to handle hw issues

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, 11 May 2012 14:10:30 -0300
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	Borislav Petkov <bp@...64.org>
CC:	Linux Edac Mailing List <linux-edac@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Doug Thompson <norsk5@...oo.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH v.23-2] RAS: use tracepoint to handle hw issues

Em 11-05-2012 14:06, Borislav Petkov escreveu:
> From Documentation/SubmittingPatches:
> 
> "2) Describe your changes.
> 
> Describe the technical detail of the change(s) your patch includes.
> 
> Be as specific as possible."
> 
> "use tracepoint to handle hw issues" is not specific - it is bullshit
> bingo with a random word generator.
> 
> I'm getting tired of this crap: either take the suggestion as is,
> without randomly changing it for no reason whatsoever, or give a good
> reason why it is not a good suggestion and propose a better one!
> 
> Randomly changing it in the next version of the patch for another, even
> crappier one doesn't help.

Well, tell me what title you want for this patch, instead of coming with
offending comments like above, and I'll change it to match your desire.

Regards,
Mauro
--
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/