linux-kernel - Re: [PATCH v4.16-rc4 1/2] x86/vdso: on Intel, VDSO should handle CLOCK_MONOTONIC

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]

Date:   Mon, 12 Mar 2018 09:24:29 +0100
From:   Ingo Molnar <mingo@...nel.org>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Jason Vas Dias <jason.vas.dias@...il.com>, x86@...nel.org,
        LKML <linux-kernel@...r.kernel.org>, andi <andi@...stfloor.org>
Subject: Re: [PATCH v4.16-rc4 1/2] x86/vdso: on Intel, VDSO should handle
 CLOCK_MONOTONIC_RAW


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

> On Mon, Mar 12, 2018 at 08:24:13AM +0100, Ingo Molnar wrote:
> 
> >  - Code quality of the submitted patches is atrocious, please run them through
> >    scripts/checkpatch.pl (and make sure they pass) to at least enable the reading 
> >    of them.
> 
> I'd suggest also reading: Documentation/CodingStyle

Yeah, a careful reading of Documentation/process/submitting-patches.rst will 
include:

  4) Style-check your changes
  ---------------------------

  Check your patch for basic style violations, details of which can be
  found in
  :ref:`Documentation/process/coding-style.rst <codingstyle>`.
  Failure to do so simply wastes
  the reviewers time and will get your patch rejected, probably
  without even being read.


Thanks,

	Ingo