From: Hajime Tazaki<thehajime@gmail.com>
To: benjamin.berg@intel.com
Cc: linux-um@lists.infradead.org
Subject: Re: [PATCH] um: move thread info into task
Date: Tue, 05 Nov 2024 10:33:20 +0900 [thread overview]
Message-ID: <m2jzdih3bz.wl-thehajime@gmail.com> (raw)
In-Reply-To: <083d8c0460d4774698a972102f893f92770a4b0d.camel@intel.com>
On Mon, 04 Nov 2024 17:17:05 +0900,
Berg, Benjamin wrote:
> > 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.
>
> Oh. Probably the easiest is to just get rid of "struct cpu_task" and
> then copy the definition of cpu_tasks over. i.e.
>
> extern void * cpu_tasks[];
>
> at that point.
thanks, this works for me.
-- Hajime
next prev parent reply other threads:[~2024-11-05 1:33 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
2024-11-04 8:17 ` Berg, Benjamin
2024-11-05 1:33 ` Hajime Tazaki [this message]
-- 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=m2jzdih3bz.wl-thehajime@gmail.com \
--to=thehajime@gmail.com \
--cc=benjamin.berg@intel.com \
--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 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).