public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: kernel test robot <fengguang.wu@intel.com>
Cc: Erico Nunes <erico.nunes@datacom.ind.br>, LKP <lkp@01.org>,
	linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
	wfg@linux.intel.com
Subject: Re: [i2c: dev] d6760b14d4:  BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff8800091b4c49
Date: Sat, 28 May 2016 09:12:34 +0200	[thread overview]
Message-ID: <20160528071234.GA1714@katana> (raw)
In-Reply-To: <57493af0.akIr4abjopweDkBu%fengguang.wu@intel.com>

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

> 0day kernel testing robot got the below dmesg and the first bad commit is
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

So, I got a success message from buildbot "[wsa:i2c/for-next]
72a71f869c95dc11b73f09fe18c593d4a0618c3f BUILD SUCCESS".

I assume now that the above message covers only compile-testing while
linus master tree also gets boot testing? Correct?

I was under the impression before that the above message also covers
simple boot tests.

Thanks,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-05-28  7:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-28  6:30 [i2c: dev] d6760b14d4: BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff8800091b4c49 kernel test robot
2016-05-28  7:12 ` Wolfram Sang [this message]
2016-05-28  7:24   ` Fengguang Wu
2016-05-28  7:32     ` Wolfram Sang
2016-05-28 10:14       ` Fengguang Wu

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=20160528071234.GA1714@katana \
    --to=wsa@the-dreams.de \
    --cc=erico.nunes@datacom.ind.br \
    --cc=fengguang.wu@intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=wfg@linux.intel.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