All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <wfg@linux.intel.com>
To: Matt Fleming <matt.fleming@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Boot error: x86/efi/ioremap kconfig:x86_64-nfsroot commit:a790068
Date: Thu, 17 May 2012 14:59:22 +0800	[thread overview]
Message-ID: <20120517065922.GA11817@localhost> (raw)
In-Reply-To: <1337236495.27692.27.camel@mfleming-mobl1.ger.corp.intel.com>

Hi Matt,

On Thu, May 17, 2012 at 07:34:55AM +0100, Matt Fleming wrote:
> On Thu, 2012-05-17 at 11:06 +0800, wfg@linux.intel.com wrote:
> > Hi Matt,
> > 
> > FYI, starting from this commit, the kernel immediately reboots in my
> > kvm boot tests..
> 
> Hi Fengguang,
> 
> Yeah, this commit is broken. I pushed it to my repository so that I
> could test it on all of my machines, but quickly discovered that it
> contains some bugs.

OK, I got it.

> How come you are running are kernel built from that branch? I only
> created it yesterday. The majority of branches in my repository are work
> in progress, at least until they appear in a pull request on lkml. Which
> means they may contain blatantly broken commits.

I happen to be building a kernel test backend for our team and
hopefully for the wider kernel community.

What I do is to fetch a number of git trees (including yours) into my
test server, iterate through *all* remote branches and test out *every
single* commits there.

> But anyway, thanks for testing as it confirms that the commit is indeed
> buggy!

My pleasure :)

Thanks,
Fengguang

  reply	other threads:[~2012-05-17  6:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17  3:06 Boot error: x86/efi/ioremap kconfig:x86_64-nfsroot commit:a790068 wfg
2012-05-17  6:34 ` Matt Fleming
2012-05-17  6:59   ` Fengguang Wu [this message]
2012-05-17  8:11     ` Matt Fleming
2012-05-17 12:27       ` 0day kernel testing back-end 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=20120517065922.GA11817@localhost \
    --to=wfg@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@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 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.