[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72k2so3ZcqA3iRziGY=Shd_B1=qGoXXROeAF7Y3+pDmqyA@mail.gmail.com>
Date: Thu, 12 Sep 2019 10:24:01 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Jens Axboe <axboe@...nel.dk>,
Dan Carpenter <dan.carpenter@...cle.com>,
Dave Jiang <dave.jiang@...el.com>,
ksummit <ksummit-discuss@...ts.linuxfoundation.org>,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
Vishal Verma <vishal.l.verma@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
bpf@...r.kernel.org
Subject: Re: [Ksummit-discuss] [PATCH v2 3/3] libnvdimm, MAINTAINERS:
Maintainer Entry Profile
On Thu, Sep 12, 2019 at 9:43 AM Dan Williams <dan.j.williams@...el.com> wrote:
>
> Now I come to find that CodingStyle has settled on clang-format (in
> the last 15 months) as the new standard which is a much better answer
> to me than a manually specified style open to interpretation. I'll
> take a look at getting libnvdimm converted over.
Note that clang-format cannot do everything as we want within the
kernel just yet, but it is a close enough approximation -- it is near
the point where we could simply agree to use it and stop worrying
about styling issues. However, that would mean everyone needs to have
a recent clang-format available, which I think is the biggest obstacle
at the moment.
Cheers,
Miguel
Powered by blists - more mailing lists