The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Jonathan Woithe <jwoithe@just42.net>
Cc: Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Micha?? K??pie?? <kernel@kempniu.pl>,
	LKML <linux-kernel@vger.kernel.org>,
	Darren Hart <dvhart@linux.intel.com>,
	platform-driver-x86@vger.kernel.org,
	Darren Hart <dvhart@infradead.org>,
	lkp@01.org
Subject: Re: [lkp-robot] [platform/x86]  a869ab5dab: BUG:unable_to_handle_kernel
Date: Mon, 27 Feb 2017 09:31:08 +0800	[thread overview]
Message-ID: <20170227013108.GC32284@yexl-desktop> (raw)
In-Reply-To: <20170227011143.GI3807@marvin.atrad.com.au>

On 02/27, Jonathan Woithe wrote:
>On Mon, Feb 27, 2017 at 09:04:14AM +0800, kernel test robot wrote:
>> FYI, we noticed the following commit:
>> 
>> commit: a869ab5dabf6ec5327a3b2bb366eccf80b207d76 ("platform/x86: fujitsu-laptop: only register backlight device if FUJ02B1 is present")
>> git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git testing
>> 
>> in testcase: boot
>> 
>> on test machine: qemu-system-i386 -enable-kvm -m 360M
>> 
>> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>This is due to the accidental merge of patch 08/10 in the patch series. 
>This was spotted by Michael and I understand Andy is addressing the
>oversight.

Got it, thanks for watching the report.

Thanks,
Xiaolong
>
>Regards
>  jonathan

      reply	other threads:[~2017-02-27  1:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27  1:04 [lkp-robot] [platform/x86] a869ab5dab: BUG:unable_to_handle_kernel kernel test robot
2017-02-27  1:11 ` Jonathan Woithe
2017-02-27  1:31   ` Ye Xiaolong [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=20170227013108.GC32284@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dvhart@infradead.org \
    --cc=dvhart@linux.intel.com \
    --cc=jwoithe@just42.net \
    --cc=kernel@kempniu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=platform-driver-x86@vger.kernel.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