From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 50BBAC5ACAE for ; Thu, 12 Sep 2019 08:24:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 272792084F for ; Thu, 12 Sep 2019 08:24:17 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="bobU2/X+" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730259AbfILIYQ (ORCPT ); Thu, 12 Sep 2019 04:24:16 -0400 Received: from mail-lj1-f193.google.com ([209.85.208.193]:38208 "EHLO mail-lj1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730179AbfILIYP (ORCPT ); Thu, 12 Sep 2019 04:24:15 -0400 Received: by mail-lj1-f193.google.com with SMTP id y23so22383737ljn.5; Thu, 12 Sep 2019 01:24:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ECkS2puFAK1gVjPinpMaI687BSxI+r7g336/1esz1k0=; b=bobU2/X+jXrG7Z7VhdAPWfrQEBrRDHgblPscgg39+wUJnCf7d4fx3qf6vcFFVvxSkN 3U4gbkvDhjbCnuW8meMQgC2Ft3e3FFwa0KHF1D5u7qW7MBU1GnNfd/QMkK8wWUaaRqCB 3JpC+A70eitPZT6pl0sNnHh2A+r/Bjvb6UnMxMWGl1ObfMLIR+F5cnwsHKrEwhjq8yyf MAFpuPAHwSYnNDLUlhili68ZfGdf+ruL/K0+YDRvDT04U78lShW4wiNWlvwbwU67SIo/ T3D0trHu4hTkAJJSD3d30zL/Ox1rPT250C9erYGII76G3/3XIUEY41WiGKx5RXmDT1UJ x+xA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ECkS2puFAK1gVjPinpMaI687BSxI+r7g336/1esz1k0=; b=LRerhYz0dapsDal6WCveyZMFx6etC+hACuljn9qOP2PqzEDl5sbz0bzqv4G/rduYCU 1siAsCRX00wZ4sIbyqC/ZU1+agBDd/gNp6GupK8marOQgciS8RfiPbKkqa5NGQe6nLm0 8xZPybx2LdIs/c9yhRAwYDx9f++RMmeS3hGEom4K4ZD981a1KdqX8SApvnpb5S1WyMlA Gm2/fTzhW0GpEPg2ExLEr5AftXOfKDNo1nOB2TgzLX/0C1Pyy85eT251NWmMipXtXQ+z 0vnopwRNX+oqxvMCRVL53i3lMDcNvutXYvNZUAlysaM59XY3cO8f4R0lMe05syXo/Jm2 xDCQ== X-Gm-Message-State: APjAAAXT+zcodJ6gyXxIxECUsgigFun1DQD+aKMKn84oJn6IFwoZOvWj W6l/JFKHgyPOkFV2eMIeKS8XL7+MLSoJUnuOELc= X-Google-Smtp-Source: APXvYqwJdAIg0MN468eMceiqvbqhEFZIaSKfHpA6hbEW7p8IU8l3e2/DQsQGc8lPdxLHrAXG/fVObo9RcVpmFUoxXg8= X-Received: by 2002:a2e:9555:: with SMTP id t21mr9396134ljh.93.1568276653052; Thu, 12 Sep 2019 01:24:13 -0700 (PDT) MIME-Version: 1.0 References: <156821692280.2951081.18036584954940423225.stgit@dwillia2-desk3.amr.corp.intel.com> <156821693963.2951081.11214256396118531359.stgit@dwillia2-desk3.amr.corp.intel.com> <20190911184332.GL20699@kadam> <9132e214-9b57-07dc-7ee2-f6bc52e960c5@kernel.dk> In-Reply-To: From: Miguel Ojeda Date: Thu, 12 Sep 2019 10:24:01 +0200 Message-ID: Subject: Re: [Ksummit-discuss] [PATCH v2 3/3] libnvdimm, MAINTAINERS: Maintainer Entry Profile To: Dan Williams Cc: Jens Axboe , Dan Carpenter , Dave Jiang , ksummit , linux-nvdimm , Vishal Verma , Linux Kernel Mailing List , bpf@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 12, 2019 at 9:43 AM Dan Williams 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