kernel-hardening - Re: [PATCH v2 1/4] perf-security: document perf

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.1902111514550.3197@nanos.tec.linutronix.de>
Date: Mon, 11 Feb 2019 15:15:55 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Alexey Budankov <alexey.budankov@...ux.intel.com>
cc: Jonatan Corbet <corbet@....net>, Kees Cook <keescook@...omium.org>, 
    Ingo Molnar <mingo@...hat.com>, Peter Zijlstra <peterz@...radead.org>, 
    Jann Horn <jannh@...gle.com>, Arnaldo Carvalho de Melo <acme@...nel.org>, 
    Jiri Olsa <jolsa@...hat.com>, Namhyung Kim <namhyung@...nel.org>, 
    Alexander Shishkin <alexander.shishkin@...ux.intel.com>, 
    Andi Kleen <ak@...ux.intel.com>, Mark Rutland <mark.rutland@....com>, 
    Tvrtko Ursulin <tvrtko.ursulin@...ux.intel.com>, 
    "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>, 
    "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>, 
    linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/4] perf-security: document perf_events/Perf resource
 control

On Mon, 11 Feb 2019, Alexey Budankov wrote:
> On 11.02.2019 1:34, Thomas Gleixner wrote:
> > On Thu, 7 Feb 2019, Alexey Budankov wrote:
> > 
> > General note: Please stay in the 80 char limit for all of the text.
> 
> Yes, sure. [PATCH v2 4/4] implements wrapping at 72 columns.

So you provide crappy formatted stuff first, just to reformat it at the
end. I'm missing the logic behind that.

Thanks,

	tglx

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.