linux-kernel - Re: [pchecks v2 0/2] percpu v3: Implement Preemption checks for __this

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: <20131004083033.GA1658@gmail.com>
Date:	Fri, 4 Oct 2013 10:30:33 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Christoph Lameter <cl@...ux.com>, Tejun Heo <tj@...nel.org>,
	akpm@...uxfoundation.org, Steven Rostedt <srostedt@...hat.com>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [pchecks v2 0/2] percpu v3: Implement Preemption checks for
 __this_cpu operations

* Peter Zijlstra <peterz@...radead.org> wrote:

> User-Agent: quilt/0.50-1
> 
> You might want to upgrade your quilt the latest version is 0.60-1 and
> there's talk of actually releasing something newer.

Another technical problem with the submission is the lack of 'PATCH' tags 
for the patches - it's the standard and ther are folks search lkml based 
on that pattern.

See Documentation/SubmittingPatches:

 | 11) Include PATCH in the subject
 |
 | Due to high e-mail traffic to Linus, and to linux-kernel, it is common 
 | convention to prefix your subject line with [PATCH].  This lets Linus 
 | and other kernel developers more easily distinguish patches from other 
 | e-mail discussions.

Note that all of the technical problems we noted need to be fixed before 
the next resubmission, not just some.

Thanks,

	Ingo
--
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/