All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Juergen Gross <jgross@suse.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: Tree for Jun 2 (x86/xen)
Date: Tue, 2 Jun 2020 17:47:19 -0400	[thread overview]
Message-ID: <4e5e87cb-daa9-fc75-bf12-401a912bb3dd@oracle.com> (raw)
In-Reply-To: <8bc4e983-7563-20f2-2c15-3cea055ae264@infradead.org>

On 6/2/20 11:18 AM, Randy Dunlap wrote:
> On 6/2/20 3:37 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> News: The merge window has opened, so please do *not* add v5.9 material
>> to your linux-next included branches until after v5.8-rc1 has been
>> released.
>>
>> Changes since 20200529:
>>
> on x86_64:
>
>   CC      arch/x86/xen/suspend_hvm.o
> In file included from ../include/xen/interface/hvm/params.h:24:0,
>                  from ../include/xen/hvm.h:6,
>                  from ../arch/x86/xen/suspend_hvm.c:5:
> ../include/xen/interface/hvm/hvm_op.h:29:5: error: unknown type name ‘domid_t’


(+Thomas)


This has been addressed by
https://lore.kernel.org/lkml/159101612916.17951.7492360776296750785.tip-bot2@tip-bot2/


-boris



>      domid_t  domid;    /* IN */
>      ^~~~~~~
> ../include/xen/interface/hvm/hvm_op.h:33:1: warning: data definition has no type or storage class
>  DEFINE_GUEST_HANDLE_STRUCT(xen_hvm_param);
>  ^~~~~~~~~~~~~~~~~~~~~~~~~~
> ../include/xen/interface/hvm/hvm_op.h:33:1: error: type defaults to ‘int’ in declaration of ‘DEFINE_GUEST_HANDLE_STRUCT’ [-Werror=implicit-int]
> ../include/xen/interface/hvm/hvm_op.h:33:1: warning: parameter names (without types) in function declaration
> ../include/xen/interface/hvm/hvm_op.h:39:5: error: unknown type name ‘domid_t’
>      domid_t  domid;
>      ^~~~~~~
> ../include/xen/interface/hvm/hvm_op.h:44:1: warning: data definition has no type or storage class
>  DEFINE_GUEST_HANDLE_STRUCT(xen_hvm_pagetable_dying_t);
>  ^~~~~~~~~~~~~~~~~~~~~~~~~~
> ../include/xen/interface/hvm/hvm_op.h:44:1: error: type defaults to ‘int’ in declaration of ‘DEFINE_GUEST_HANDLE_STRUCT’ [-Werror=implicit-int]
> ../include/xen/interface/hvm/hvm_op.h:56:5: error: unknown type name ‘domid_t’
>      domid_t domid;
>      ^~~~~~~
> ../include/xen/interface/hvm/hvm_op.h:63:1: warning: data definition has no type or storage class
>  DEFINE_GUEST_HANDLE_STRUCT(xen_hvm_get_mem_type);
>  ^~~~~~~~~~~~~~~~~~~~~~~~~~
> ../include/xen/interface/hvm/hvm_op.h:63:1: error: type defaults to ‘int’ in declaration of ‘DEFINE_GUEST_HANDLE_STRUCT’ [-Werror=implicit-int]
> ../include/xen/interface/hvm/hvm_op.h:63:1: warning: parameter names (without types) in function declaration
>
>
> Full randconfig file is attached.
>


WARNING: multiple messages have this Message-ID (diff)
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Juergen Gross <jgross@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 2 (x86/xen)
Date: Tue, 2 Jun 2020 17:47:19 -0400	[thread overview]
Message-ID: <4e5e87cb-daa9-fc75-bf12-401a912bb3dd@oracle.com> (raw)
In-Reply-To: <8bc4e983-7563-20f2-2c15-3cea055ae264@infradead.org>

On 6/2/20 11:18 AM, Randy Dunlap wrote:
> On 6/2/20 3:37 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> News: The merge window has opened, so please do *not* add v5.9 material
>> to your linux-next included branches until after v5.8-rc1 has been
>> released.
>>
>> Changes since 20200529:
>>
> on x86_64:
>
>   CC      arch/x86/xen/suspend_hvm.o
> In file included from ../include/xen/interface/hvm/params.h:24:0,
>                  from ../include/xen/hvm.h:6,
>                  from ../arch/x86/xen/suspend_hvm.c:5:
> ../include/xen/interface/hvm/hvm_op.h:29:5: error: unknown type name ‘domid_t’


(+Thomas)


This has been addressed by
https://lore.kernel.org/lkml/159101612916.17951.7492360776296750785.tip-bot2@tip-bot2/


-boris



>      domid_t  domid;    /* IN */
>      ^~~~~~~
> ../include/xen/interface/hvm/hvm_op.h:33:1: warning: data definition has no type or storage class
>  DEFINE_GUEST_HANDLE_STRUCT(xen_hvm_param);
>  ^~~~~~~~~~~~~~~~~~~~~~~~~~
> ../include/xen/interface/hvm/hvm_op.h:33:1: error: type defaults to ‘int’ in declaration of ‘DEFINE_GUEST_HANDLE_STRUCT’ [-Werror=implicit-int]
> ../include/xen/interface/hvm/hvm_op.h:33:1: warning: parameter names (without types) in function declaration
> ../include/xen/interface/hvm/hvm_op.h:39:5: error: unknown type name ‘domid_t’
>      domid_t  domid;
>      ^~~~~~~
> ../include/xen/interface/hvm/hvm_op.h:44:1: warning: data definition has no type or storage class
>  DEFINE_GUEST_HANDLE_STRUCT(xen_hvm_pagetable_dying_t);
>  ^~~~~~~~~~~~~~~~~~~~~~~~~~
> ../include/xen/interface/hvm/hvm_op.h:44:1: error: type defaults to ‘int’ in declaration of ‘DEFINE_GUEST_HANDLE_STRUCT’ [-Werror=implicit-int]
> ../include/xen/interface/hvm/hvm_op.h:56:5: error: unknown type name ‘domid_t’
>      domid_t domid;
>      ^~~~~~~
> ../include/xen/interface/hvm/hvm_op.h:63:1: warning: data definition has no type or storage class
>  DEFINE_GUEST_HANDLE_STRUCT(xen_hvm_get_mem_type);
>  ^~~~~~~~~~~~~~~~~~~~~~~~~~
> ../include/xen/interface/hvm/hvm_op.h:63:1: error: type defaults to ‘int’ in declaration of ‘DEFINE_GUEST_HANDLE_STRUCT’ [-Werror=implicit-int]
> ../include/xen/interface/hvm/hvm_op.h:63:1: warning: parameter names (without types) in function declaration
>
>
> Full randconfig file is attached.
>



  reply	other threads:[~2020-06-02 21:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 10:37 linux-next: Tree for Jun 2 Stephen Rothwell
2020-06-02 14:36 ` linux-next: Tree for Jun 2 (vfio) Randy Dunlap
2020-06-02 15:16   ` Alex Williamson
2020-06-02 19:56     ` Alex Williamson
2020-06-02 15:18 ` linux-next: Tree for Jun 2 (x86/xen) Randy Dunlap
2020-06-02 15:18   ` Randy Dunlap
2020-06-02 21:47   ` Boris Ostrovsky [this message]
2020-06-02 21:47     ` Boris Ostrovsky

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=4e5e87cb-daa9-fc75-bf12-401a912bb3dd@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sstabellini@kernel.org \
    --cc=tglx@linutronix.de \
    --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.