From: Christoph Hellwig <hch@lst.de>
To: Kari Argillander <kari.argillander@gmail.com>
Cc: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
ntfs3@lists.linux.dev, Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>
Subject: Re: [PATCH v3 1/3] fs/ntfs3: Fix one none utf8 char in source file
Date: Wed, 18 Aug 2021 07:33:00 +0200 [thread overview]
Message-ID: <20210818053300.GA9165@lst.de> (raw)
In-Reply-To: <20210818010649.412912-2-kari.argillander@gmail.com>
On Wed, Aug 18, 2021 at 04:06:47AM +0300, Kari Argillander wrote:
> In one source file there is for some reason non utf8 char. But hey this
> is fs development so this kind of thing might happen.
Pleaese also refomat these comments while you're at it. While going
over 80 characters is ok in exceptions for readability that is per
definition never the case for a block comment.
next prev parent reply other threads:[~2021-08-18 5:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 1:06 [PATCH v3 0/3] fs/ntfs3: Use kernel alloc wrappers and fix warnings Kari Argillander
2021-08-18 1:06 ` [PATCH v3 1/3] fs/ntfs3: Fix one none utf8 char in source file Kari Argillander
2021-08-18 5:33 ` Christoph Hellwig [this message]
2021-08-18 8:56 ` Kari Argillander
2021-08-18 1:06 ` [PATCH v3 2/3] fs/ntfs3: Do not use driver own alloc wrappers Kari Argillander
2021-08-24 8:04 ` Christoph Hellwig
2021-08-18 1:06 ` [PATCH v3 3/3] fs/ntfs3: Use kcalloc/kmalloc_array over kzalloc/kmalloc Kari Argillander
2021-08-24 8:04 ` Christoph Hellwig
2021-08-18 5:23 ` [PATCH v3 0/3] fs/ntfs3: Use kernel alloc wrappers and fix warnings Christoph Hellwig
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=20210818053300.GA9165@lst.de \
--to=hch@lst.de \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=joe@perches.com \
--cc=kari.argillander@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
/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