Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Jonathan Corbet <corbet@lwn.net>
To:     Kari Argillander <kari.argillander@gmail.com>,
        Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
        ntfs3@lists.linux.dev
Cc:     Kari Argillander <kari.argillander@gmail.com>,
        linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Doc/fs/ntfs3: Fix rst format and make it cleaner
In-Reply-To: <20210909215753.34138-1-kari.argillander@gmail.com>
References: <20210909215753.34138-1-kari.argillander@gmail.com>
Date:   Tue, 14 Sep 2021 14:53:41 -0600
Message-ID: <878rzyev56.fsf@meer.lwn.net>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

Kari Argillander <kari.argillander@gmail.com> writes:

> Current ntfs3 rst documentation is broken. I turn table to list table as
> this is current Linux documentation quide line. Simple table also did
> not quite work in our situation as we need to span rows together.
>
> It still look quite good as text so we did not loss anything. This will
> also make diffing quite bit more pleasure.
>
> Signed-off-by: Kari Argillander <kari.argillander@gmail.com>
> ---
> As this is pretty new to me and Konstantin I CC Jonathan because he is
> maintainer of documentation section. Do you want to get all
> documentation patches to you about ntfs3? This probably still goes
> through our tree? I ask because checkpatch will give your address also
> and it is not clear to me at least should I send these to you also.

Don't hesitate to CC people when in doubt - it's the kernel way :)

As for merging, documentation patches should go through whatever is the
best path.  Some subsystem maintainers want me to take them, others want
to handle them themselves.  It sounds like you're in the latter camp, so
I'll assume I don't need to apply this one; let me know if I've
misunderstood.

Thanks,

jon