public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: Miaohe Lin <linmiaohe@huawei.com>,
	axboe@kernel.dk, ebiederm@xmission.com,
	madhuparnabhowmik10@gmail.com, gustavoars@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] signal: clean up codestyle
Date: Tue, 1 Sep 2020 18:39:05 +0200	[thread overview]
Message-ID: <20200901163904.GC4386@redhat.com> (raw)
In-Reply-To: <20200901122047.7hzztrssvr72wb2d@wittgenstein>

On 09/01, Christian Brauner wrote:
>
> On Tue, Sep 01, 2020 at 07:58:00AM -0400, Miaohe Lin wrote:
> > No functional change intended.
>
> Hey Miaohe,
>
> Thank you for the patch.
> I'm sure this is well-intended but afaict the whole file has more or
> less a consistent style already where e.g. sig-1 without spaces seems to
> be preferred. The same for the casts where most places use a single
> space.
>
> Now, I know CodingStyle.rst is on your side at least when it comes to
> the first point:
>
> Use one space around (on each side of) most binary and ternary operators,
> such as any of these::
>
> 	=  +  -  <  >  *  /  %  |  &  ^  <=  >=  ==  !=  ?  :
>
> but then you'd need to change each place in kernel/signal.c where that
> is currently not the case.

Or simply leave this code alone ;)

To be honest I do not like the very idea of enforce-coding-style patches,
coding style is very personal and even this trivial (but imho pointless)
change can complicate the backporting of some bugfix. I hit this problem
quite often.

Oleg.


  reply	other threads:[~2020-09-01 16:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 11:58 [PATCH] signal: clean up codestyle Miaohe Lin
2020-09-01 12:20 ` Christian Brauner
2020-09-01 16:39   ` Oleg Nesterov [this message]
2020-09-01 16:42     ` Christian Brauner
  -- strict thread matches above, loose matches on Subject: below --
2020-09-01 12:47 linmiaohe
2020-09-02  1:34 linmiaohe
2020-09-02  8:47 ` Christian Brauner
2020-09-03  1:54 linmiaohe

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=20200901163904.GC4386@redhat.com \
    --to=oleg@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=christian.brauner@ubuntu.com \
    --cc=ebiederm@xmission.com \
    --cc=gustavoars@kernel.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madhuparnabhowmik10@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