From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Dave Chinner <david@fromorbit.com>
Cc: <ntfs3@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 1/3] fs/ntfs3: Refactoring of indx_find function
Date: Mon, 30 May 2022 19:15:48 +0300 [thread overview]
Message-ID: <d9d51b3f-e59a-1a50-8c11-ff1b2036271d@paragon-software.com> (raw)
In-Reply-To: <20220528000620.GH3923443@dread.disaster.area>
This was caused by an incorrect account setting in Thunderbird.
Thanks for catching this.
On 5/28/22 03:06, Dave Chinner wrote:
> On Fri, May 27, 2022 at 05:21:03PM +0300, Almaz Alexandrovich wrote:
>> This commit makes function a bit more readable
>>
>> Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
>
> This looks wrong. The email is from
>
> "From: Almaz Alexandrovich <almaz.alexandrovich@paragon-software.com>"
>
> So it looks like the S-o-B has the wrong email address in it. All
> the patches have this same problem.
>
> Cheers,
>
> Dave.
next prev parent reply other threads:[~2022-05-30 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 14:15 [PATCH 0/3] fs/ntfs3: Refactoring and bugfix Almaz Alexandrovich
2022-05-27 14:21 ` [PATCH 1/3] fs/ntfs3: Refactoring of indx_find function Almaz Alexandrovich
2022-05-27 16:07 ` Joe Perches
2022-05-30 17:11 ` Konstantin Komarov
2022-05-28 0:06 ` Dave Chinner
2022-05-30 16:15 ` Konstantin Komarov [this message]
2022-05-27 14:22 ` [PATCH 2/3] fs/ntfs3: Fix double free on remount Almaz Alexandrovich
2022-05-27 14:22 ` [PATCH 3/3] fs/ntfs3: Refactor ni_try_remove_attr_list function Almaz Alexandrovich
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=d9d51b3f-e59a-1a50-8c11-ff1b2036271d@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--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