From: Rongqing Li <rongqing.li@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH][v2] e2fsprogs: fix the ptest
Date: Fri, 13 Nov 2015 08:03:09 +0800 [thread overview]
Message-ID: <564528BD.2050705@windriver.com> (raw)
In-Reply-To: <CAJTo0LYVnvcYH2NZBtKtupO_bjnr9MKFWYRH5519q8+5xJdY3w@mail.gmail.com>
On 2015年11月12日 18:13, Burton, Ross wrote:
>
> On 12 November 2015 at 03:04, <rongqing.li@windriver.com
> <mailto:rongqing.li@windriver.com>> wrote:
>
> +cache_inode.patch speeds up the making ext* filesystem, but it leads
> +to the m_bigjournal ptest failure; In fact, when
> ext2fs_extent_node_split
> +is called, the cache goal should be reset
> +
> +the patch fixes the m_bigjournal ptest failure, and does not lost the
> +speed.
>
>
> Please edit the patch, instead of patching a patch.
I did not patching a patch, I create a new patch
-Roy
>
> Ross
--
Best Reagrds,
Roy | RongQing Li
next prev parent reply other threads:[~2015-11-13 0:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 3:04 [PATCH][v2] e2fsprogs: fix the ptest rongqing.li
2015-11-12 10:13 ` Burton, Ross
2015-11-13 0:03 ` Rongqing Li [this message]
2015-11-16 16:17 ` Burton, Ross
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=564528BD.2050705@windriver.com \
--to=rongqing.li@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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