linux-kernel.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, nixiaoming@huawei.com,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Davidlohr Bueso <dave@stgolabs.net>
Subject: Re: [PATCH] fs/proc: Introduce list_for_each_table_entry for proc sysctl
Date: Fri, 15 Apr 2022 15:35:19 -0700	[thread overview]
Message-ID: <YlnzJxHPqc96rFE+@bombadil.infradead.org> (raw)
In-Reply-To: <20220411051205.6694-1-tangmeng@uniontech.com>

On Mon, Apr 11, 2022 at 01:12:05PM +0800, Meng Tang wrote:
> Use the list_for_each_table_entry macro to optimize the scenario
> of traverse ctl_table. This make the code neater and easier to
> understand.
> 
> Suggested-by: Davidlohr Bueso<dave@stgolabs.net>
> Signed-off-by: Meng Tang <tangmeng@uniontech.com>

Thanks! Queued onto sysctl-testing [0].

Feel free to let start sending in the rest of the stuff you were working
on. But please note I'll wait to push this to sysctl-next to get testing
under linux-next until this gets at least some compilation testing
without issues from sysctl-testing.

[0] https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/log/?h=sysctl-testing

  Luis

  reply	other threads:[~2022-04-15 22:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  5:12 [PATCH] fs/proc: Introduce list_for_each_table_entry for proc sysctl Meng Tang
2022-04-15 22:35 ` Luis Chamberlain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-15  6:06 Meng Tang
2022-04-06 22:28 ` 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=YlnzJxHPqc96rFE+@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=dave@stgolabs.net \
    --cc=keescook@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nixiaoming@huawei.com \
    --cc=tangmeng@uniontech.com \
    --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;
as well as URLs for NNTP newsgroup(s).