From: Christoph Hellwig <hch@lst.de>
To: "Huang, Ying" <ying.huang@linux.intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
LKML <linux-kernel@vger.kernel.org>,
0day robot <fengguang.wu@intel.com>
Subject: Re: [lkp] [configfs] 7d3c5f36a5: BUG: unable to handle kernel
Date: Mon, 29 Feb 2016 09:54:30 +0100 [thread overview]
Message-ID: <20160229085430.GA8582@lst.de> (raw)
In-Reply-To: <874mcrzzmr.fsf@yhuang-dev.intel.com>
On Mon, Feb 29, 2016 at 04:31:24PM +0800, Huang, Ying wrote:
> Christoph Hellwig <hch@lst.de> writes:
>
> > The version below should fix it, how do I inject that into the bot
> > again?
>
> Just commit it in your tree. The bot will fetch and test it
> automatically although you cannot get all boot test success notification
> now yet. We are working on that.
The patch shouldn't actually be in any tree yet..
prev parent reply other threads:[~2016-02-29 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 1:12 [lkp] [configfs] 7d3c5f36a5: BUG: unable to handle kernel kernel test robot
2016-02-29 8:19 ` Christoph Hellwig
2016-02-29 8:31 ` Huang, Ying
2016-02-29 8:54 ` Christoph Hellwig [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=20160229085430.GA8582@lst.de \
--to=hch@lst.de \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ying.huang@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