[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <be3c626c2e9d14fe2fa9d0403bc02832231cc437.camel@perches.com>
Date: Thu, 12 Sep 2019 01:15:37 -0700
From: Joe Perches <joe@...ches.com>
To: Dan Williams <dan.j.williams@...el.com>,
Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: linux-nvdimm <linux-nvdimm@...ts.01.org>,
Dan Carpenter <dan.carpenter@...cle.com>,
Vishal Verma <vishal.l.verma@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
Keith Busch <keith.busch@...el.com>,
Ira Weiny <ira.weiny@...el.com>,
Oliver O'Halloran <oohall@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/13] nvdimm: Use more common kernel coding style
On Thu, 2019-09-12 at 01:00 -0700, Dan Williams wrote:
> Hi Joe,
>
> On Wed, Sep 11, 2019 at 7:55 PM Joe Perches <joe@...ches.com> wrote:
> > Rather than have a local coding style, use the typical kernel style.
>
> I'd rather automate this. I'm going to do once-over with clang-format
> and see what falls out.
I am adding Miguel Ojeda to the cc's.
Of course you are welcome to try it, but I believe that
clang-format doesn't work all that well yet.
It's more a work in progress rather than a "standard".
I believe you'll find that the patch series I sent
ends up with a rather more typical kernel style.
I suggest you try to apply the series I sent and then
run clang-format on that and see the differences.
Ideally one day, something tool like clang-format
might be locally applied by every developer for their
own personal style with some other neutral style the
content actually distributed.
cheers, Joe
Powered by blists - more mailing lists