From: Miaohe Lin <linmiaohe@huawei.com>
To: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: add myself as a memory-failure reviewer
Date: Wed, 8 Jun 2022 20:27:39 +0800 [thread overview]
Message-ID: <07a5fb28-a9b2-3c77-79fd-c1dc7dbe755e@huawei.com> (raw)
In-Reply-To: <20220607224210.GA1400450@hori.linux.bs1.fc.nec.co.jp>
On 2022/6/8 6:42, HORIGUCHI NAOYA(堀口 直也) wrote:
> On Tue, Jun 07, 2022 at 10:51:35PM +0800, Miaohe Lin wrote:
>> I have been focusing on mm for the past two years. e.g. fixing bugs,
>> cleaning up the code and reviewing. I would like to help maintainers
>> and people working on memory-failure by reviewing their work.
>>
>> Let me be Cc'd on patches related to memory-failure.
>>
>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>
> Thank you for raising a hand, this is really nice.
That's my pleasure. I will try my best to be qualified for this position. ;)
>
> Acked-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
Thanks!
>
>> ---
>> MAINTAINERS | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 6e4ad450bf3c..6430aebfe296 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -9136,6 +9136,7 @@ F: drivers/media/platform/st/sti/hva
>>
>> HWPOISON MEMORY FAILURE HANDLING
>> M: Naoya Horiguchi <naoya.horiguchi@nec.com>
>> +R: Miaohe Lin <linmiaohe@huawei.com>
>> L: linux-mm@kvack.org
>> S: Maintained
>> F: mm/hwpoison-inject.c
>> --
>> 2.23.0
prev parent reply other threads:[~2022-06-08 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 14:51 Miaohe Lin
2022-06-07 22:42 ` HORIGUCHI NAOYA(堀口 直也)
2022-06-08 12:27 ` Miaohe Lin [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=07a5fb28-a9b2-3c77-79fd-c1dc7dbe755e@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
/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