linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	pali@kernel.org, dsterba@suse.cz, aaptel@suse.com,
	Matthew Wilcox <willy@infradead.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	Joe Perches <joe@perches.com>,
	mark@harmstone.com, nborisov@suse.com,
	linux-ntfs-dev@lists.sourceforge.net, anton@tuxera.com,
	Dan <dan.carpenter@oracle.com>, Christoph Hellwig <hch@lst.de>,
	ebiggers@kernel.org, andy.lavr@gmail.com
Subject: Re: [PATCH v22 00/10] NTFS read-write driver GPL implementation by Paragon Software
Date: Thu, 4 Mar 2021 09:30:49 +0100	[thread overview]
Message-ID: <CANiq72nRpxe5M5rsBdWe_2tEpGju7Oe0bBhOdwMBa6MHkHi_Qg@mail.gmail.com> (raw)
In-Reply-To: <20210301160102.2884774-1-almaz.alexandrovich@paragon-software.com>

On Thu, Mar 4, 2021 at 1:09 AM Konstantin Komarov
<almaz.alexandrovich@paragon-software.com> wrote:
>
> - use clang-format 11.0 instead of 10.0 to format code

Out of curiosity: was this due to some specific reason? i.e. have you
found it provides better output? (it is useful to know this to justify
later an increase of the minimum version etc.)

Thanks!

Cheers,
Miguel

      parent reply	other threads:[~2021-03-04  8:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 16:00 [PATCH v22 00/10] NTFS read-write driver GPL implementation by Paragon Software Konstantin Komarov
2021-03-01 16:00 ` [PATCH v22 01/10] fs/ntfs3: Add headers and misc files Konstantin Komarov
2021-03-01 16:00 ` [PATCH v22 02/10] fs/ntfs3: Add initialization of super block Konstantin Komarov
2021-03-01 16:00 ` [PATCH v22 03/10] fs/ntfs3: Add bitmap Konstantin Komarov
2021-03-01 16:00 ` [PATCH v22 04/10] fs/ntfs3: Add file operations and implementation Konstantin Komarov
2021-03-01 16:00 ` [PATCH v22 05/10] fs/ntfs3: Add attrib operations Konstantin Komarov
2021-03-01 16:00 ` [PATCH v22 06/10] fs/ntfs3: Add compression Konstantin Komarov
2021-03-01 16:00 ` [PATCH v22 07/10] fs/ntfs3: Add NTFS journal Konstantin Komarov
2021-03-01 16:01 ` [PATCH v22 08/10] fs/ntfs3: Add Kconfig, Makefile and doc Konstantin Komarov
2021-03-01 16:01 ` [PATCH v22 09/10] fs/ntfs3: Add NTFS3 in fs/Kconfig and fs/Makefile Konstantin Komarov
2021-03-05  4:04   ` kernel test robot
2021-03-01 16:01 ` [PATCH v22 10/10] fs/ntfs3: Add MAINTAINERS Konstantin Komarov
2021-03-04  8:30 ` Miguel Ojeda [this message]

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=CANiq72nRpxe5M5rsBdWe_2tEpGju7Oe0bBhOdwMBa6MHkHi_Qg@mail.gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=aaptel@suse.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=andy.lavr@gmail.com \
    --cc=anton@tuxera.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=ebiggers@kernel.org \
    --cc=hch@lst.de \
    --cc=joe@perches.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntfs-dev@lists.sourceforge.net \
    --cc=mark@harmstone.com \
    --cc=nborisov@suse.com \
    --cc=pali@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).