From: Johan Hovold <johan@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Johan Hovold <johan@kernel.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Shreeya Patel <shreeya.patel23498@gmail.com>,
greybus-dev@lists.linaro.org
Subject: Re: [PATCH] Staging: greybus: Match alignment with open parenthesis.
Date: Fri, 28 Jul 2017 11:01:55 +0200 [thread overview]
Message-ID: <20170728090155.GK27516@localhost> (raw)
In-Reply-To: <20170728044932.GB31077@kroah.com>
On Thu, Jul 27, 2017 at 09:49:32PM -0700, Greg KH wrote:
> On Mon, Jul 24, 2017 at 10:08:37AM +0300, Dan Carpenter wrote:
> > I don't understand why greybus has to be special instead of the same as
> > everything else. Who cares about this stuff really? Just do whatever
> > is easiest and most common.
>
> It's not special, and --strict should apply here as long as it is in
> staging. So I'll apply these types of things to prevent people from
> feeling like they wasted their time fixing something up and getting it
> rejected for no good reason.
Your call, but I do think that this is taking the checkpatch exercise
too far.
What we're talking about here are neither checkpatch ERRORs nor
WARNINGs, but that third category of CHECK notifications that are
output only when the switch --strict, or it's more aptly named alias
--subjective, is specified.
Just like we don't blindly apply patches addressing every ERROR or
WARNING, I think we should not accept every patch addressing these
subjective CHECK notifications.
These flags are useful when people are submitting new code; and most of
the CHECKs enabled by --subjective do seem reasonable, at least in my
(subjective) opinion.
I personally think that neither OPEN_PARENTHESIS nor LINE_SPACING do
or should apply everywhere however, and that the final call should be
left up to the author and/or maintainer of the code in question.
But yes, greybus is still in staging so it is ultimately your call.
I will see if I can find some spare cycles to start migrating at least
the core bits out of staging either way.
Johan
next prev parent reply other threads:[~2017-07-28 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 8:39 [PATCH] Staging: greybus: Match alignment with open parenthesis Shreeya Patel
2017-07-23 8:47 ` Johan Hovold
2017-07-23 12:10 ` Dan Carpenter
2017-07-23 12:54 ` Johan Hovold
2017-07-24 7:08 ` Dan Carpenter
2017-07-28 4:49 ` Greg KH
2017-07-28 9:01 ` Johan Hovold [this message]
2017-07-28 4:48 ` Greg KH
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=20170728090155.GK27516@localhost \
--to=johan@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shreeya.patel23498@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;
as well as URLs for NNTP newsgroup(s).