From: Borislav Petkov <bp@alien8.de>
To: Nick Krause <xerofoify@gmail.com>
Cc: Davidlohr Bueso <davidlohr@hp.com>,
Thomas Gleixner <tglx@linutronix.de>,
Richard Henderson <rth@twiddle.net>,
ink@jurassic.park.msu.ru, Matt Turner <mattst88@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Al Viro <viro@zeniv.linux.org.uk>,
linux-alpha@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Joe Perches <joe@perches.com>, Theodore Ts'o <tytso@mit.edu>
Subject: Re: Alpha Checkpatch Errors
Date: Fri, 18 Jul 2014 10:55:10 +0200 [thread overview]
Message-ID: <20140718085510.GA11098@pd.tnic> (raw)
In-Reply-To: <CAPDOMVh-gtvTP6OY_fM31NcM_ez==f1fBNgV_YaoSXuQcUtiRQ@mail.gmail.com>
On Thu, Jul 17, 2014 at 11:24:45PM -0400, Nick Krause wrote:
> > Nick, are you human?
> >
> Yes I am human.
It doesn't look like it. *Every-f*ckin-body* is telling you to stop
doing this FIXME bullshit but you continue like a bot which cannot parse
answer mails.
Just answer me one thing: why are you even doing this? Are you doing this
because
* you want to help with kernel development
* see your name in git logs
* ...
or simply because you're doing some sick experiment to see how long you
can bother people on lkml with senseless crap and are secretly giggling
nasty at all the pissed answers you get?
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-07-18 8:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 22:03 Alpha Checkpatch Errors Nick Krause
2014-07-17 22:17 ` Thomas Gleixner
2014-07-18 3:01 ` Nick Krause
2014-07-18 3:21 ` Davidlohr Bueso
2014-07-18 3:24 ` Nick Krause
2014-07-18 8:55 ` Borislav Petkov [this message]
2014-07-18 10:18 ` Peter Zijlstra
2014-07-18 11:58 ` Steven Rostedt
2014-07-18 17:08 ` Nick Krause
2014-07-18 17:31 ` Steven Rostedt
2014-07-18 17:35 ` Nick Krause
2014-07-18 17:50 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140718085510.GA11098@pd.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=davidlohr@hp.com \
--cc=ink@jurassic.park.msu.ru \
--cc=joe@perches.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rth@twiddle.net \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=xerofoify@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox