From: Namjae Jeon <linkinjeon@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: brauner@kernel.org, anton@tuxera.com,
linux-ntfs-dev@lists.sourceforge.net,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH v2] ntfs: Add myself as a reviewer
Date: Wed, 17 May 2023 17:26:59 +0900 [thread overview]
Message-ID: <CAKYAXd_=kXjKnmfiSEuTLG0fd6Ezj+7_R_ZSWntbvUgQ9Hyx0w@mail.gmail.com> (raw)
In-Reply-To: <4125c148-a4f4-edd2-3009-0283246f8a95@gmail.com>
2023-05-17 16:37 GMT+09:00, Bagas Sanjaya <bagasdotme@gmail.com>:
> On 5/17/23 14:07, Namjae Jeon wrote:
>> I'm volunteering to help review patches for current unmaintained
>> ntfs filesytem.
>>
>> Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
>> ---
>> MAINTAINERS | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index e2fd64c2ebdc..c2cecb2059d7 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -14928,6 +14928,7 @@ F: drivers/ntb/hw/intel/
>>
>> NTFS FILESYSTEM
>> M: Anton Altaparmakov <anton@tuxera.com>
>> +R: Namjae Jeon <linkinjeon@kernel.org>
>> L: linux-ntfs-dev@lists.sourceforge.net
>> S: Supported
>> W: http://www.tuxera.com/
>
> Acked-by: Bagas Sanjaya <bagasdotme@gmail.com>
Thanks for your ack!
>
> Anyway, what about also adding linux-mm list so that akpm can
> pick patches?
Hm.. I think that MM folks probably don't like to see fs patches on mm list...
And as far as I know, Christian is going to picks up the ntfs patches.
Christian, right?
>
> --
> An old man doll... just what I always wanted! - Clara
>
>
next prev parent reply other threads:[~2023-05-17 8:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230517070739.6505-1-linkinjeon@kernel.org>
2023-05-17 7:37 ` Bagas Sanjaya
2023-05-17 8:26 ` Namjae Jeon [this message]
2023-05-17 8:43 ` Christian Brauner
2023-05-17 9:28 ` Namjae Jeon
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='CAKYAXd_=kXjKnmfiSEuTLG0fd6Ezj+7_R_ZSWntbvUgQ9Hyx0w@mail.gmail.com' \
--to=linkinjeon@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anton@tuxera.com \
--cc=bagasdotme@gmail.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
/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