All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>, Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
	Russell King <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH -next] sched/headers: ARM needs asm/paravirt_api_clock.h
Date: Mon, 21 Mar 2022 08:38:22 -0700	[thread overview]
Message-ID: <Yjib7hDFRFEOwaWf@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20220316204146.14000-1-rdunlap@infradead.org>

On Wed, Mar 16, 2022 at 01:41:46PM -0700, Randy Dunlap wrote:
> Add <asm/paravirt_api_clock.h> for arch/arm/.
> 
> Fixes this build error:
> 
> In file included from ../kernel/sched/core.c:81:
> ../kernel/sched/sched.h:87:11: fatal error: asm/paravirt_api_clock.h: No such file or directory
>    87 | # include <asm/paravirt_api_clock.h>
> 
> Fixes: 4ff8f2ca6ccd ("sched/headers: Reorganize, clean up and optimize kernel/sched/sched.h dependencies")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Russell King <linux@armlinux.org.uk>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: patches@armlinux.org.uk

Reviewed-by: Nathan Chancellor <nathan@kernel.org>

This needs to go into -tip to avoid breaking the build for ARM
all{mod,yes}config. It looks like the pull has already been sent though
:/

> ---
> KernelVersion: linux-next-20220316
> 
>  arch/arm/include/asm/paravirt_api_clock.h |    1 +
>  1 file changed, 1 insertion(+)
> 
> --- /dev/null
> +++ linux-next-20220316/arch/arm/include/asm/paravirt_api_clock.h
> @@ -0,0 +1 @@
> +#include <asm/paravirt.h>
> 

WARNING: multiple messages have this Message-ID (diff)
From: Nathan Chancellor <nathan@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>, Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
	Russell King <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH -next] sched/headers: ARM needs asm/paravirt_api_clock.h
Date: Mon, 21 Mar 2022 08:38:22 -0700	[thread overview]
Message-ID: <Yjib7hDFRFEOwaWf@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20220316204146.14000-1-rdunlap@infradead.org>

On Wed, Mar 16, 2022 at 01:41:46PM -0700, Randy Dunlap wrote:
> Add <asm/paravirt_api_clock.h> for arch/arm/.
> 
> Fixes this build error:
> 
> In file included from ../kernel/sched/core.c:81:
> ../kernel/sched/sched.h:87:11: fatal error: asm/paravirt_api_clock.h: No such file or directory
>    87 | # include <asm/paravirt_api_clock.h>
> 
> Fixes: 4ff8f2ca6ccd ("sched/headers: Reorganize, clean up and optimize kernel/sched/sched.h dependencies")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Ingo Molnar <mingo@kernel.org>
> Cc: Russell King <linux@armlinux.org.uk>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: patches@armlinux.org.uk

Reviewed-by: Nathan Chancellor <nathan@kernel.org>

This needs to go into -tip to avoid breaking the build for ARM
all{mod,yes}config. It looks like the pull has already been sent though
:/

> ---
> KernelVersion: linux-next-20220316
> 
>  arch/arm/include/asm/paravirt_api_clock.h |    1 +
>  1 file changed, 1 insertion(+)
> 
> --- /dev/null
> +++ linux-next-20220316/arch/arm/include/asm/paravirt_api_clock.h
> @@ -0,0 +1 @@
> +#include <asm/paravirt.h>
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-03-21 15:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 20:41 [PATCH -next] sched/headers: ARM needs asm/paravirt_api_clock.h Randy Dunlap
2022-03-16 20:41 ` Randy Dunlap
2022-03-21 15:38 ` Nathan Chancellor [this message]
2022-03-21 15:38   ` Nathan Chancellor
2022-03-22  7:53   ` Ingo Molnar
2022-03-22  7:53     ` Ingo Molnar
2022-03-22  8:02 ` [tip: sched/core] sched/headers: ARM needs asm/paravirt_api_clock.h too tip-bot2 for Randy Dunlap

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=Yjib7hDFRFEOwaWf@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mingo@kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=rdunlap@infradead.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.