From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <jbeulich@suse.com>,
Frediano Ziglio <frediano.ziglio@cloud.com>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>, xen-devel@lists.xenproject.org
Subject: Re: [PATCH] x86/setup: Make setup.h header self contained
Date: Wed, 30 Oct 2024 11:35:34 +0000 [thread overview]
Message-ID: <89b2d609-f298-4dc8-b893-dc52468694ae@citrix.com> (raw)
In-Reply-To: <8984f1da-d4bb-4ab7-b1dc-bcc23c180abc@suse.com>
On 30/10/2024 11:17 am, Jan Beulich wrote:
> On 30.10.2024 12:15, Frediano Ziglio wrote:
>> On Wed, Oct 30, 2024 at 10:59 AM Jan Beulich <jbeulich@suse.com> wrote:
>>> On 30.10.2024 11:44, Frediano Ziglio wrote:
>>>> The header uses rangeset structure typedef which definition
>>>> is not included.
>>> And it doesn't need to be. For
>>>
>>> int remove_xen_ranges(struct rangeset *r);
>>>
>>> we don't need ...
>>>
>>>> --- a/xen/arch/x86/include/asm/setup.h
>>>> +++ b/xen/arch/x86/include/asm/setup.h
>>>> @@ -2,6 +2,7 @@
>>>> #define __X86_SETUP_H_
>>>>
>>>> #include <xen/multiboot.h>
>>>> +#include <xen/rangeset.h>
>>>> #include <asm/numa.h>
>>>>
>>>> extern const char __2M_text_start[], __2M_text_end[];
>>> ... this, a mere
>>>
>>> struct rangeset;
>>>
>>> forward decl will suffice.
>>>
>>> Jan
>>>
>> It's true, but for the same reason, we could avoid including
>> "xen/multiboot.h" and use "struct module" instead of "module_t".
> Indeed. I'd even question the need for that typedef.
Please don't got playing with includes of multiboot.h. All you'll do is
interfere with Daniel's in-progress series.
Most includes are getting removed.
~Andrew
prev parent reply other threads:[~2024-10-30 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 10:44 [PATCH] x86/setup: Make setup.h header self contained Frediano Ziglio
2024-10-30 10:59 ` Jan Beulich
2024-10-30 11:15 ` Frediano Ziglio
2024-10-30 11:17 ` Jan Beulich
2024-10-30 11:35 ` Andrew Cooper [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=89b2d609-f298-4dc8-b893-dc52468694ae@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=frediano.ziglio@cloud.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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.