From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: kbuild test robot <lkp@intel.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
<kbuild-all@01.org>, <xen-devel@lists.xensource.com>,
<linux-kernel@vger.kernel.org>, <david.vrabel@citrix.com>,
<konrad.wilk@oracle.com>, <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH 2/2] hvc_xen: fix xenboot for DomUs
Date: Wed, 24 Feb 2016 15:48:01 +0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1602241547080.17248@kaball.uk.xensource.com> (raw)
In-Reply-To: <201602242008.Td9zQF7s%fengguang.wu@intel.com>
Hi kbuild test robot,
you are awesome as always. I'll fix it in the next version.
Thanks,
Stefano
On Wed, 24 Feb 2016, kbuild test robot wrote:
> Hi Stefano,
>
> [auto build test WARNING on tty/tty-testing]
> [also build test WARNING on v4.5-rc5 next-20160223]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
>
> url: https://github.com/0day-ci/linux/commits/Stefano-Stabellini/hvc_xen-add-earlycon-support/20160224-203006
> base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
> config: x86_64-randconfig-x009-201608 (attached as .config)
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All warnings (new ones prefixed by >>):
>
> drivers/tty/hvc/hvc_xen.c: In function 'xenboot_setup_console':
> >> drivers/tty/hvc/hvc_xen.c:637:1: warning: control reaches end of non-void function [-Wreturn-type]
> }
> ^
>
> vim +637 drivers/tty/hvc/hvc_xen.c
>
> 621 }
> 622 if (off < len)
> 623 domU_write_console(0, string+off, len-off);
> 624 }
> 625
> 626 #ifdef CONFIG_EARLY_PRINTK
> 627 static int xenboot_setup_console(struct console *console, char *string)
> 628 {
> 629 static struct xencons_info xenboot;
> 630
> 631 if (xen_initial_domain())
> 632 return 0;
> 633 if (!xen_pv_domain())
> 634 return -ENODEV;
> 635
> 636 xen_early_pv_console_init(&xenboot, 0);
> > 637 }
> 638
> 639 static void xenboot_write_console(struct console *console, const char *string,
> 640 unsigned len)
> 641 {
> 642 if (!xen_pv_domain())
> 643 return;
> 644
> 645 dom0_write_console(0, string, len);
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
prev parent reply other threads:[~2016-02-24 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 12:22 [0/2] hvc_xen: fix xenboot on x86 and export to ARM Stefano Stabellini
2016-02-24 12:23 ` [PATCH 1/2] hvc_xen: add earlycon support Stefano Stabellini
2016-02-24 14:43 ` Boris Ostrovsky
2016-02-24 15:55 ` Stefano Stabellini
[not found] ` <20160224171842.GA9463@char.us.oracle.com>
2016-02-24 17:22 ` [Xen-devel] " Andrew Cooper
2016-02-25 12:00 ` Stefano Stabellini
2016-02-25 11:53 ` Stefano Stabellini
2016-02-24 12:23 ` [PATCH 2/2] hvc_xen: fix xenboot for DomUs Stefano Stabellini
2016-02-24 12:53 ` kbuild test robot
2016-02-24 15:48 ` Stefano Stabellini [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=alpine.DEB.2.02.1602241547080.17248@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=kbuild-all@01.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=xen-devel@lists.xensource.com \
/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
all inboxes | Powered by JetHome®