From: Marco Elver <elver@google.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: paulmck@kernel.org, mark.rutland@arm.com,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>, Joe Perches <joe@perches.com>
Subject: Re: [PATCH] init_task: Include <linux/rbtree.h> in the right file
Date: Sun, 4 Dec 2022 14:55:11 +0100 [thread overview]
Message-ID: <Y4ymv/BxtulPrM47@elver.google.com> (raw)
In-Reply-To: <f06e810735c49a611e7dc75715f0689b5f7e87c6.1670153931.git.christophe.jaillet@wanadoo.fr>
[+Cc Ingo, who had been working on lots of include improvements.]
The Cc list is odd -- it appears that get_maintainers.pl is broken on
init_task.c:
$> ./scripts/get_maintainer.pl init/init_task.c
Mark Rutland <mark.rutland@arm.com> (commit_signer:1/1=100%)
"Paul E. McKenney" <paulmck@kernel.org> (commit_signer:1/1=100%)
Marco Elver <elver@google.com> (commit_signer:1/1=100%,authored:1/1=100%,removed_lines:5/5=100%)
linux-kernel@vger.kernel.org (open list)
What's going on here?
On Sun, Dec 04, 2022 at 12:39PM +0100, Christophe JAILLET wrote:
> There is no need to include <linux/rbtree.h> in init_task.h.
> Move it to the right place, in kernel/cred.c which uses RB_ROOT_CACHED.
>
> This is a follow-up of commit 4e7e3adbba52 ("Expand various INIT_* macros
> and remove") which moved things from init_task.h to init_task.c
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> Let see if build-bots agree with me!
>
> This patch depends on [1] and [2].
> All these patches are related to init_task.h simplification.
>
> They are unrelated and can be applied separately, but as they modify more
> or less the same place in the same file, there may be some merge conflict.
>
> [1]: https://lore.kernel.org/all/1a3d5bd51b7807471a913f8fa621e5a4ecd08e6a.1670100520.git.christophe.jaillet@wanadoo.fr/
> [2]: https://lore.kernel.org/all/94c8f2123a8833b61d84a662ec35f9c070cdf4dd.1670147823.git.christophe.jaillet@wanadoo.fr/
> ---
> include/linux/init_task.h | 1 -
> init/init_task.c | 1 +
> 2 files changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/init_task.h b/include/linux/init_task.h
> index 6d2c4ea4c97a..e18a6c6f6fd9 100644
> --- a/include/linux/init_task.h
> +++ b/include/linux/init_task.h
> @@ -9,7 +9,6 @@
> #include <linux/ipc.h>
> #include <linux/user_namespace.h>
> #include <linux/seqlock.h>
> -#include <linux/rbtree.h>
> #include <linux/refcount.h>
> #include <linux/sched/autogroup.h>
> #include <net/net_namespace.h>
> diff --git a/init/init_task.c b/init/init_task.c
> index ff6c4b9bfe6b..2392c0a67fb7 100644
> --- a/init/init_task.c
> +++ b/init/init_task.c
> @@ -2,6 +2,7 @@
> #include <linux/init_task.h>
> #include <linux/export.h>
> #include <linux/mqueue.h>
> +#include <linux/rbtree.h>
> #include <linux/sched.h>
> #include <linux/sched/sysctl.h>
> #include <linux/sched/rt.h>
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-12-04 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 11:39 [PATCH] init_task: Include <linux/rbtree.h> in the right file Christophe JAILLET
2022-12-04 13:55 ` Marco Elver [this message]
2022-12-04 17:16 ` Joe Perches
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=Y4ymv/BxtulPrM47@elver.google.com \
--to=elver@google.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.