From: Hajime Tazaki<thehajime@gmail.com>
To: benjamin@sipsolutions.net
Cc: linux-um@lists.infradead.org, benjamin.berg@intel.com
Subject: Re: [PATCH] um: move thread info into task
Date: Mon, 04 Nov 2024 17:08:45 +0900 [thread overview]
Message-ID: <m2ldxzh14i.wl-thehajime@gmail.com> (raw)
In-Reply-To: <20241103150534.1368018-1-benjamin@sipsolutions.net>
Hello,
this is a great clean up I think.
I've also applied my tentative nommu patch and works fine with minor modifications.
On Mon, 04 Nov 2024 00:05:34 +0900,
Benjamin Berg wrote:
> diff --git a/arch/um/include/asm/current.h b/arch/um/include/asm/current.h
> new file mode 100644
> index 000000000000..93ee89e56372
> --- /dev/null
> +++ b/arch/um/include/asm/current.h
> @@ -0,0 +1,24 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +#ifndef __ASM_CURRENT_H
> +#define __ASM_CURRENT_H
> +
> +#include <linux/compiler.h>
> +
> +#ifndef __ASSEMBLY__
> +
> +#include <as-layout.h>
with this include, I guess <generated/asm-offsets.h> is now in a
circular dependency.
after only applying this patch onto uml/next, and make mrproper
ARCH=um, I cannot build UML kernel with defconfig.
> diff --git a/arch/um/os-Linux/signal.c b/arch/um/os-Linux/signal.c
> index 1978eaa557e9..87d31a0672c0 100644
> --- a/arch/um/os-Linux/signal.c
> +++ b/arch/um/os-Linux/signal.c
> @@ -186,47 +186,14 @@ static void (*handlers[_NSIG])(int sig, struct siginfo *si, mcontext_t *mc) = {
> [SIGUSR1] = sigusr1_handler,
> };
>
> +extern char cpu0_irqstack[];
> +
maybe this line isn't needed ?
-- Hajime
next prev parent reply other threads:[~2024-11-04 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 15:05 [PATCH] um: move thread info into task Benjamin Berg
2024-11-04 8:08 ` Hajime Tazaki [this message]
2024-11-04 8:17 ` Berg, Benjamin
2024-11-05 1:33 ` Hajime Tazaki
-- strict thread matches above, loose matches on Subject: below --
2024-11-08 9:08 Benjamin Berg
2024-11-09 1:03 ` Hajime Tazaki
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=m2ldxzh14i.wl-thehajime@gmail.com \
--to=thehajime@gmail.com \
--cc=benjamin.berg@intel.com \
--cc=benjamin@sipsolutions.net \
--cc=linux-um@lists.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.