linux-parisc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Kees Cook <keescook@chromium.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	amir73il@gmail.com, Andrew Morton <akpm@linux-foundation.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Daniel Axtens <dja@axtens.net>,
	"David S. Miller" <davem@davemloft.net>,
	Dominik Brodowski <linux@dominikbrodowski.net>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Eric Dumazet <edumazet@google.com>,
	federico.vaga@vaga.pv.it,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Helge Deller <deller@gmx.de>, Joshua Kinard <kumba@gentoo.org>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	linux-ide@vger.kernel.org,
	linux-m68k <linux-m68k@lists.linux-m68k.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux MIPS Mailing List <linux-mips@linux-mips.org>,
	MTD Maling List <linux-mtd@lists.infradead.org>,
	Parisc List <linux-parisc@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	scsi <linux-scsi@vger.kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	netdev <netdev@vger.kernel.org>,
	nouveau@lists.freedesktop.org, pabeni@redhat.com,
	Paul Burton <paul.burton@mips.com>,
	Petr Mladek <pmladek@suse.com>, Rob Herring <robh@kernel.org>,
	sean.wang@mediatek.com,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	shannon.nelson@oracle.com, Stefano Brivio <sbrivio@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	"Tobin C. Harding" <me@tobin.cc>,
	makita.toshiaki@lab.ntt.co.jp,
	Willem de Bruijn <willemb@google.com>,
	yhs@fb.com, yanjun.zhu@oracle.com
Subject: Re: [PATCH RFC 00/15] Zero ****s, hugload of hugs <3
Date: Sat, 1 Dec 2018 09:20:03 +0100	[thread overview]
Message-ID: <CAMuHMdUkpLWm5NZmYj=uMgVncw6ZOb7j9KxFoDGhrnr7vzpx_w@mail.gmail.com> (raw)
In-Reply-To: <20181130151459.3ca2f5c8@lwn.net>

Hi Jon,

On Fri, Nov 30, 2018 at 11:15 PM Jonathan Corbet <corbet@lwn.net> wrote:
> On Fri, 30 Nov 2018 14:12:19 -0800
> Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> wrote:
>
> > As a maintainer myself (and based on somewhat disturbed feedback from
> > other maintainers) I can only make the conclusion that nobody knows what
> > the responsibility part here means.
> >
> > I would interpret, if I read it like at lawyer at least, that even for
> > existing code you would need to do the changes postmorterm.
> >
> > Is this wrong interpretation?  Should I conclude that I made a mistake
> > by reading the CoC and trying to understand what it *actually* says?
> > After this discussion, I can say that I understand it less than before.
>
> Have you read Documentation/process/code-of-conduct-interpretation.rst?
> As has been pointed out, it contains a clear answer to how things should
> be interpreted here.

Indeed:

| Contributions submitted for the kernel should use appropriate language.
| Content that already exists predating the Code of Conduct will not be
| addressed now as a violation.

However:

| Inappropriate language can be seen as a
| bug, though; such bugs will be fixed more quickly if any interested
| parties submit patches to that effect.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  parent reply	other threads:[~2018-12-01  8:20 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181130192737.15053-1-jarkko.sakkinen@linux.intel.com>
2018-11-30 19:27 ` [PATCH RFC 05/15] parisc: replace **** with a hug Jarkko Sakkinen
2018-11-30 22:48   ` Dennis Clarke
2018-11-30 23:03     ` Jarkko Sakkinen
2018-11-30 23:05   ` Diego Viola
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
     [not found]         ` <2007856.n5V9iKLVsV@eth7>
2018-11-30 20:42           ` David Miller
2018-11-30 20:43           ` Steven Rostedt
2018-12-01  4:08           ` Jarkko Sakkinen
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 23:28                       ` Jarkko Sakkinen
2018-12-01  8:20                 ` Geert Uytterhoeven [this message]
2018-12-07 13:39                   ` Eric Curtin
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 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='CAMuHMdUkpLWm5NZmYj=uMgVncw6ZOb7j9KxFoDGhrnr7vzpx_w@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=amir73il@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=corbet@lwn.net \
    --cc=dave@stgolabs.net \
    --cc=davem@davemloft.net \
    --cc=deller@gmx.de \
    --cc=dja@axtens.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=edumazet@google.com \
    --cc=federico.vaga@vaga.pv.it \
    --cc=geert+renesas@glider.be \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=keescook@chromium.org \
    --cc=kumba@gentoo.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=makita.toshiaki@lab.ntt.co.jp \
    --cc=matthias.bgg@gmail.com \
    --cc=me@tobin.cc \
    --cc=netdev@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=pabeni@redhat.com \
    --cc=paul.burton@mips.com \
    --cc=pmladek@suse.com \
    --cc=robh@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sbrivio@redhat.com \
    --cc=sean.wang@mediatek.com \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=shannon.nelson@oracle.com \
    --cc=willemb@google.com \
    --cc=yanjun.zhu@oracle.com \
    --cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).