linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: 苏家训 <sujiaxun@uniontech.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: keescook@chromium.org, yzaikin@google.com,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: move oom_kill sysctls to their own file
Date: Tue, 15 Feb 2022 16:23:48 +0800	[thread overview]
Message-ID: <7058b3c2-5c22-f163-1f1a-3906d9b7e047@uniontech.com> (raw)
In-Reply-To: <Ygtdgp9P8+887VMm@bombadil.infradead.org>



在 2022/2/15 16:00, Luis Chamberlain 写道:
> On Tue, Feb 15, 2022 at 03:56:10PM +0800, 苏家训 wrote:
>> I checked the patch using ./scripts/checkpatch.pl and found no errors.
> 
> ./scripts/get_maintainer.pl, not checkpatch.
> 
>    Luis
>>   
> 
I checked the patch using ./scripts/get_maintainer.pl. Is there 
something wrong with my sending?
src/linux-next$ ./scripts/get_maintainer.pl 
0001-mm-move-oom_kill-sysctls-to-their-own-file.patch
Luis Chamberlain <mcgrof@kernel.org> (maintainer: PROC SYSCTL)
Kees Cook <keescook@chromium.org> (maintainer:PROC SYSCTL)
Iurii Zaikin <yzaikin@google.com> (maintainer:PROC SYSCTL)
Andrew Morton <akpm@linux-foundation.org> (maintainer:MEMORY MANAGEMENT)
linux-kernel@vger.kernel.org (open list)
linux-fsdevel@vger.kernel.org (open list: PROC SYSCTL)
linux-mm@kvack.org (open list:MEMORY MANAGEMENT)





  reply	other threads:[~2022-02-15  8:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  3:02 sujiaxun
2022-02-15  7:29 ` Luis Chamberlain
2022-02-15  7:56   ` 苏家训
2022-02-15  8:00     ` Luis Chamberlain
2022-02-15  8:23       ` 苏家训 [this message]
2022-02-15  8:36         ` Luis Chamberlain

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=7058b3c2-5c22-f163-1f1a-3906d9b7e047@uniontech.com \
    --to=sujiaxun@uniontech.com \
    --cc=akpm@linux-foundation.org \
    --cc=keescook@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mcgrof@kernel.org \
    --cc=yzaikin@google.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