linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Meng Tang <tangmeng@uniontech.com>
Cc: keescook@chromium.org, yzaikin@google.com, ebiederm@xmission.com,
	willy@infradead.org, kbuild-all@lists.01.org,
	nixiaoming@huawei.com, nizhen@uniontech.com,
	zhanglianjie@uniontech.com, sujiaxun@uniontech.com,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] fs/proc: optimize register ctl_tables
Date: Wed, 18 Jan 2023 16:10:52 -0800	[thread overview]
Message-ID: <Y8iKjJYMFRSthxzn@bombadil.infradead.org> (raw)
In-Reply-To: <Y7xWUQQIJYLMk5fO@bombadil.infradead.org>

On Mon, Jan 09, 2023 at 10:00:49AM -0800, Luis Chamberlain wrote:
> On Tue, Mar 08, 2022 at 07:22:51PM +0800, kernel test robot wrote:
> > Hi Meng,
> > 
> > Thank you for the patch! Perhaps something to improve:
> 
> Meng, can you re-send with a fix? We're early in the merge window to
> help test stuff now.

*re-poke* if you can't work on this please let me know!

  Luis

  reply	other threads:[~2023-01-19  0:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 11:23 [PATCH v5 1/2] fs/proc: optimize register ctl_tables Meng Tang
2022-03-04 11:23 ` [PATCH v5 2/2] fs/proc: sysctl: remove register ctl_table end with empty Meng Tang
2022-03-08 11:22 ` [PATCH v5 1/2] fs/proc: optimize register ctl_tables kernel test robot
2023-01-09 18:00   ` Luis Chamberlain
2023-01-19  0:10     ` Luis Chamberlain [this message]
2023-03-02  1:12       ` Luis Chamberlain
2023-03-02  2:45         ` Meng Tang
2023-03-02 19:52           ` Luis Chamberlain
2023-03-02  2:56         ` Meng Tang

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=Y8iKjJYMFRSthxzn@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=ebiederm@xmission.com \
    --cc=kbuild-all@lists.01.org \
    --cc=keescook@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nixiaoming@huawei.com \
    --cc=nizhen@uniontech.com \
    --cc=sujiaxun@uniontech.com \
    --cc=tangmeng@uniontech.com \
    --cc=willy@infradead.org \
    --cc=yzaikin@google.com \
    --cc=zhanglianjie@uniontech.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;
as well as URLs for NNTP newsgroup(s).