public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Måns Rullgård" <mans@mansr.com>
Cc: Joe Perches <joe@perches.com>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	piotrgregor@rsyncme.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Moratorium on coding style patches (was Re: [PATCH] include/linux/kernel.h: fixed coding style issues)
Date: Thu, 15 Dec 2016 09:12:56 -0800	[thread overview]
Message-ID: <20161215171256.GA27592@kroah.com> (raw)
In-Reply-To: <yw1xd1gttnjl.fsf@unicorn.mansr.com>

On Thu, Dec 15, 2016 at 11:54:54AM +0000, Måns Rullgård wrote:
> Joe Perches <joe@perches.com> writes:
> 
> > On Wed, 2016-12-14 at 18:13 +0000, Måns Rullgård wrote:
> >> Alexey Dobriyan <adobriyan@gmail.com> writes:
> >> > I call for a tree wide moratorium on pure coding style changes.
> > []
> >> I'd relax this slightly and say don't do style
> >> patches unless as a prelude to some real work.
> >
> > And exclude drivers/staging
> 
> I wouldn't mind seeing staging deleted.  What makes those drivers so
> special that they deserve to be included in the main tree without
> meeting even the most basic of standards normally required?

Because it provides both a place where people can learn in a "safe"
place, and it allows companies to get their code into the tree so that
others can use it, and it allows users to use their hardware when there
is no other driver availble and no one has done the work to get it
cleaned up yet "properly".

If you don't like staging, fine, ignore it, but don't ask to have it be
deleted if you don't even understand why it was created, why it is used,
and who it is for.

Basic education and manners people, please.

greg k-h

      parent reply	other threads:[~2016-12-15 17:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14 15:32 Moratorium on coding style patches (was Re: [PATCH] include/linux/kernel.h: fixed coding style issues) Alexey Dobriyan
2016-12-14 18:13 ` Måns Rullgård
2016-12-14 23:49   ` Joe Perches
2016-12-15 11:54     ` Måns Rullgård
2016-12-15 17:03       ` Joe Perches
2016-12-15 17:12       ` Greg KH [this message]

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=20161215171256.GA27592@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=adobriyan@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mans@mansr.com \
    --cc=piotrgregor@rsyncme.org \
    --cc=torvalds@linux-foundation.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