All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	linux-input@vger.kernel.org, xen-devel@lists.xenproject.org,
	dmitry.torokhov@gmail.com, Juergen Gross <jgross@suse.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] xen,input: try to read screen resolution for xen-kbdfront
Date: Wed, 25 Jan 2017 05:16:37 +0800	[thread overview]
Message-ID: <201701250517.UMRhpB8e%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170124120955.24898-1-jgross@suse.com>

[-- Attachment #1: Type: text/plain, Size: 932 bytes --]

Hi Juergen,

[auto build test ERROR on xen-tip/linux-next]
[also build test ERROR on v4.10-rc5]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Juergen-Gross/xen-input-try-to-read-screen-resolution-for-xen-kbdfront/20170125-010022
base:   https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git linux-next
config: x86_64-randconfig-h0-01250255 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   drivers/built-in.o: In function `xenkbd_probe':
>> xen-kbdfront.c:(.text+0x3dc506): undefined reference to `registered_fb'

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 24684 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Juergen Gross <jgross@suse.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	linux-input@vger.kernel.org, xen-devel@lists.xenproject.org,
	dmitry.torokhov@gmail.com, Juergen Gross <jgross@suse.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] xen,input: try to read screen resolution for xen-kbdfront
Date: Wed, 25 Jan 2017 05:16:37 +0800	[thread overview]
Message-ID: <201701250517.UMRhpB8e%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170124120955.24898-1-jgross@suse.com>

[-- Attachment #1: Type: text/plain, Size: 932 bytes --]

Hi Juergen,

[auto build test ERROR on xen-tip/linux-next]
[also build test ERROR on v4.10-rc5]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Juergen-Gross/xen-input-try-to-read-screen-resolution-for-xen-kbdfront/20170125-010022
base:   https://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git linux-next
config: x86_64-randconfig-h0-01250255 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   drivers/built-in.o: In function `xenkbd_probe':
>> xen-kbdfront.c:(.text+0x3dc506): undefined reference to `registered_fb'

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 24684 bytes --]

  parent reply	other threads:[~2017-01-24 21:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24 12:09 [PATCH] xen,input: try to read screen resolution for xen-kbdfront Juergen Gross
2017-01-24 18:47 ` Dmitry Torokhov
2017-01-27  6:06   ` [PATCH] xen, input: " Juergen Gross
2017-01-27  6:06   ` [PATCH] xen,input: " Juergen Gross
2017-01-24 18:47 ` [PATCH] xen, input: " Dmitry Torokhov
2017-01-24 21:16 ` kbuild test robot [this message]
2017-01-24 21:16   ` [PATCH] xen,input: " kbuild test robot
2017-01-24 21:16 ` [PATCH] xen, input: " kbuild test robot
  -- strict thread matches above, loose matches on Subject: below --
2017-01-24 12:09 Juergen Gross

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=201701250517.UMRhpB8e%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jgross@suse.com \
    --cc=kbuild-all@01.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --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.