From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paul.burton@mips.com>,
James Hogan <jhogan@kernel.org>, Joshua Kinard <kumba@gentoo.org>,
"open list:MIPS" <linux-mips@linux-mips.org>
Subject: Re: [PATCH RFC 01/15] MIPS: replace **** with a hug
Date: Fri, 30 Nov 2018 13:50:03 -0800 [thread overview]
Message-ID: <20181130215003.GH23772@linux.intel.com> (raw)
In-Reply-To: <9ba4d08d-10d1-c233-476a-c73051b8c9f5@suse.com>
On Fri, Nov 30, 2018 at 11:06:30PM +0200, Nikolay Borisov wrote:
> I find it quite ridiculous that grown up people are engaging at yet
> another coc-related conversation and are on the way to blowing it out of
> proportions. Let's focus on improving the ACTUAL code what's the point
> to bikeshed on the word?
>
> I've seen people before me comment that some comments are plainly out of
> date and that warrants their removal but otherwise nitpicking things
> like that. It seems common sense is very scant these days...
I have absolutely nothing against CoC.
If you look up from LKML, there total zero posts from criticizing of
having such. OK, maybe I find it bit too high-level, and yeah, this
patch set has been useful to know where the line is. I can go through
the commits and think more appropriate alternatives (thus the RFC-tag).
Thanks.
/Jarkko
next prev parent reply other threads:[~2018-11-30 21:50 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 19:27 [PATCH RFC 00/15] Zero ****s, hugload of hugs <3 Jarkko Sakkinen
2018-11-30 19:27 ` [PATCH RFC 01/15] MIPS: replace **** with a hug Jarkko Sakkinen
2018-11-30 19:57 ` Jarkko Sakkinen
2018-11-30 21:06 ` Nikolay Borisov
2018-11-30 21:50 ` Jarkko Sakkinen [this message]
2018-11-30 22:11 ` Nikolay Borisov
2018-11-30 21:13 ` Al Viro
2018-11-30 21:28 ` Randy Dunlap
2018-11-30 19:40 ` [PATCH RFC 00/15] Zero ****s, hugload of hugs <3 Kees Cook
2018-11-30 19:56 ` Davidlohr Bueso
2018-11-30 20:12 ` Jens Axboe
2018-11-30 20:34 ` Michael Schmitz
2018-11-30 20:35 ` David Miller
2018-11-30 20:39 ` Abuse
2018-11-30 20:42 ` David Miller
2018-11-30 20:45 ` Abuse
2018-11-30 20:43 ` Steven Rostedt
2018-11-30 21:42 ` Jarkko Sakkinen
2018-11-30 21:47 ` David Miller
2018-11-30 21:53 ` Jens Axboe
2018-11-30 20:34 ` David Miller
2018-11-30 20:55 ` Jarkko Sakkinen
2018-11-30 21:01 ` James Bottomley
2018-11-30 21:44 ` Jarkko Sakkinen
2018-11-30 21:48 ` David Miller
2018-11-30 21:54 ` Jarkko Sakkinen
2018-11-30 22:04 ` James Bottomley
2018-11-30 21:57 ` James Bottomley
2018-11-30 22:12 ` Jarkko Sakkinen
2018-11-30 22:14 ` Jonathan Corbet
2018-11-30 22:26 ` Jarkko Sakkinen
2018-11-30 22:29 ` Jarkko Sakkinen
2018-11-30 22:30 ` James Bottomley
2018-11-30 22:40 ` Jarkko Sakkinen
2018-11-30 22:26 ` James Bottomley
2018-11-30 21:02 ` Steven Rostedt
2018-11-30 21:04 ` Jonathan Corbet
2018-11-30 20:09 ` John Paul Adrian Glaubitz
2018-11-30 21:32 ` Jarkko Sakkinen
2018-11-30 20:31 ` Matthias Brugger
2018-11-30 21:34 ` Jarkko Sakkinen
2018-11-30 20:42 ` Chris Mason
2018-11-30 21:36 ` Jarkko Sakkinen
2018-11-30 21:07 ` Jarkko Sakkinen
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=20181130215003.GH23772@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jhogan@kernel.org \
--cc=kumba@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=nborisov@suse.com \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
/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;
as well as URLs for NNTP newsgroup(s).