All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: zyjzyj2000@gmail.com, linux-rdma@vger.kernel.org,
	Bob Pearson <rpearson@hpe.com>
Subject: Re: [PATCH for-next v2] RDMA/rxe: Split MEM into MR and MW
Date: Thu, 1 Apr 2021 08:30:58 -0300	[thread overview]
Message-ID: <20210401113058.GW1463678@nvidia.com> (raw)
In-Reply-To: <d542977c-54fa-b1e6-8717-616d6c5b5218@gmail.com>

On Wed, Mar 31, 2021 at 02:51:35PM -0500, Bob Pearson wrote:

> Is the long term goal to take clang-format as the default whitespace format?

Sort of. clang-format is quite close to the accepted kernel standard
and makes maintaince alot easier, but gets a bunch of stuff wrong.

> If so should I just reformat all the files in rxe now and get it over with?

We try not to do this, just fix egregious errors when you touch the
code.

There seem to be two camps on this topic:

 - Internal consistency is more important that following the normative
   style. This is the idea that if one file is insane it should stay
   consistently isane. This avoids files looking "hard to read"

 - New code should follow the normative style. Old code should be
   changed when it is touched. Files will become internally inconsistent.
   This avoids everyone doing maintenance work from having to
   understand a million different local style convections

I tend to be in the latter group. 

Especially when it comes to the annoying vertical alignment that is so
common in RDMA.

Jason

  reply	other threads:[~2021-04-01 17:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 21:24 [PATCH for-next v2] RDMA/rxe: Split MEM into MR and MW Bob Pearson
2021-03-30  7:13 ` Zhu Yanjun
2021-03-30 15:09   ` Bob Pearson
2021-03-30 20:12 ` Jason Gunthorpe
2021-03-30 20:46   ` Bob Pearson
2021-03-30 22:54     ` Jason Gunthorpe
2021-03-31 19:51       ` Bob Pearson
2021-04-01 11:30         ` Jason Gunthorpe [this message]
2021-04-03 19:00   ` Bob Pearson
2021-04-04  7:41     ` Mark Bloch
2021-04-04 16:39       ` Bob Pearson

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=20210401113058.GW1463678@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=rpearson@hpe.com \
    --cc=rpearsonhpe@gmail.com \
    --cc=zyjzyj2000@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.