From: Huang, Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [sched/idle] bb400b924e: fio.write_clat_95%_us -8% improvement
Date: Fri, 07 Apr 2017 14:12:52 +0800 [thread overview]
Message-ID: <87efx4agpn.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <070BEF4AC20468458C22969097656CD94BFB568A@shsmsx102.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
"Li, Aubrey" <aubrey.li@intel.com> writes:
>>
>> I found your commit is not correct on inn,
>>
>> $ cd /c/repo/linux
>> $ git show git show ea899bd65fc285d5753d70a7879a7332821bbc02
>> fatal: bad object ea899bd65fc285d5753d70a7879a7332821bbc02
>>
>
> The commit id does not in Linux repo, it's in my fast_idle repo, which
> I specified in the command
The /c/repo/linux is the combination of all all tested kernel, including
your repo.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2017-04-07 6:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 7:12 [lkp-robot] [sched/idle] bb400b924e: fio.write_clat_95%_us -8% improvement kernel test robot
2017-04-06 5:56 ` Li, Aubrey
2017-04-06 6:26 ` Ye Xiaolong
2017-04-06 13:54 ` Li, Aubrey
2017-04-07 1:33 ` Huang, Ying
2017-04-07 1:47 ` Li, Aubrey
2017-04-07 2:21 ` Huang, Ying
2017-04-07 3:10 ` Li, Aubrey
2017-04-07 1:46 ` Ye Xiaolong
2017-04-07 2:12 ` Li, Aubrey
2017-04-07 2:24 ` Huang, Ying
2017-04-07 5:26 ` Li, Aubrey
2017-04-07 6:02 ` Huang, Ying
2017-04-07 6:06 ` Li, Aubrey
2017-04-07 6:11 ` Ye Xiaolong
2017-04-07 6:16 ` Li, Aubrey
2017-04-07 6:25 ` Huang, Ying
2017-04-07 6:41 ` Li, Aubrey
2017-04-07 6:44 ` Huang, Ying
2017-04-07 6:51 ` Li, Aubrey
2017-04-07 6:58 ` Huang, Ying
2017-04-07 6:12 ` Huang, Ying [this message]
2017-04-07 3:34 ` Li, Aubrey
2017-04-07 3:44 ` Ye Xiaolong
2017-04-07 6:58 ` Li, Aubrey
2017-04-07 7:03 ` Huang, Ying
2017-04-07 7:12 ` Li, Aubrey
2017-04-07 7:18 ` Huang, Ying
2017-04-07 8:32 ` Du, Julie
2017-04-07 8:39 ` Li, Aubrey
2017-04-07 8:43 ` Huang, Ying
2017-04-07 8:48 ` Li, Aubrey
2017-04-07 8:53 ` Li, Aubrey
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=87efx4agpn.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=lkp@lists.01.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.