From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Alexander Gordeev" <agordeev@linux.ibm.com>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Ingo Molnar" <mingo@kernel.org>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-s390@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2 5/5] sched/vtime: do not include <asm/vtime.h> header
Date: Fri, 09 Feb 2024 13:38:01 +1000 [thread overview]
Message-ID: <CZ08GUY1Y35T.2U33WWSJN7JVH@wheely> (raw)
In-Reply-To: <e0827ac2f96d87f623575098f9d55e77351b63c6.1707422448.git.agordeev@linux.ibm.com>
On Fri Feb 9, 2024 at 6:15 AM AEST, Alexander Gordeev wrote:
> There is no architecture-specific code or data left
> that generic <linux/vtime.h> needs to know about.
> Thus, avoid the inclusion of <asm/vtime.h> header.
Nice cleanup!
Acked-by: Nicholas Piggin <npiggin@gmail.com>
>
> Reviewed-by: Frederic Weisbecker <frederic@kernel.org>
> Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
> ---
> arch/powerpc/include/asm/Kbuild | 1 -
> include/asm-generic/vtime.h | 1 -
> include/linux/vtime.h | 4 ----
> 3 files changed, 6 deletions(-)
> delete mode 100644 include/asm-generic/vtime.h
>
> diff --git a/arch/powerpc/include/asm/Kbuild b/arch/powerpc/include/asm/Kbuild
> index 61a8d5555cd7..e5fdc336c9b2 100644
> --- a/arch/powerpc/include/asm/Kbuild
> +++ b/arch/powerpc/include/asm/Kbuild
> @@ -6,5 +6,4 @@ generic-y += agp.h
> generic-y += kvm_types.h
> generic-y += mcs_spinlock.h
> generic-y += qrwlock.h
> -generic-y += vtime.h
> generic-y += early_ioremap.h
> diff --git a/include/asm-generic/vtime.h b/include/asm-generic/vtime.h
> deleted file mode 100644
> index b1a49677fe25..000000000000
> --- a/include/asm-generic/vtime.h
> +++ /dev/null
> @@ -1 +0,0 @@
> -/* no content, but patch(1) dislikes empty files */
> diff --git a/include/linux/vtime.h b/include/linux/vtime.h
> index 593466ceebed..29dd5b91dd7d 100644
> --- a/include/linux/vtime.h
> +++ b/include/linux/vtime.h
> @@ -5,10 +5,6 @@
> #include <linux/context_tracking_state.h>
> #include <linux/sched.h>
>
> -#ifdef CONFIG_VIRT_CPU_ACCOUNTING_NATIVE
> -#include <asm/vtime.h>
> -#endif
> -
> /*
> * Common vtime APIs
> */
prev parent reply other threads:[~2024-02-09 3:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 20:15 [PATCH v2 0/5] sched/vtime: vtime.h headers cleanup Alexander Gordeev
2024-02-08 20:15 ` [PATCH v2 1/5] sched/vtime: remove confusing arch_vtime_task_switch() declaration Alexander Gordeev
2024-02-09 3:28 ` Nicholas Piggin
2024-02-08 20:15 ` [PATCH v2 2/5] sched/vtime: get rid of generic vtime_task_switch() implementation Alexander Gordeev
2024-02-09 3:36 ` Nicholas Piggin
2024-02-08 20:15 ` [PATCH v2 3/5] s390/vtime: remove unused __ARCH_HAS_VTIME_TASK_SWITCH leftover Alexander Gordeev
2024-02-09 3:36 ` Nicholas Piggin
2024-02-08 20:15 ` [PATCH v2 4/5] s390/irq,nmi: include <asm/vtime.h> header directly Alexander Gordeev
2024-02-08 20:15 ` [PATCH v2 5/5] sched/vtime: do not include <asm/vtime.h> header Alexander Gordeev
2024-02-09 3:38 ` Nicholas Piggin [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=CZ08GUY1Y35T.2U33WWSJN7JVH@wheely \
--to=npiggin@gmail.com \
--cc=agordeev@linux.ibm.com \
--cc=frederic@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
/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