From: Ed Tomlinson <edt@aei.ca>
To: Forrest Liu <forrestl@synology.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: fix find_free_dev_extent() malfunction in case device tree has hole
Date: Tue, 03 Feb 2015 13:01:41 -0500 [thread overview]
Message-ID: <6a7eaaa1-ee4b-4c8f-905c-c9b6da9ba0b8@aei.ca> (raw)
In-Reply-To: <CAJSVwFP89ZSqtL1Y2E12KXE8y+hhs_JkbqWqcidcfvc920HSMw@mail.gmail.com>
Hi,
Its a great idea to test the patches before submitting. However I think
its even more importent to tell us the state of testing. eg. this is an
RFC or in production in abc's kernel, and this version is untested or has
been compile tested, boot tested, improves xfstests (before x failures out
of z, after the patch the number of failures was y, where y<x).
A little bit of info like this will help those of us using the info in the
lists and should aid getting your patches into the kernel faster.
Thanks
Ed
On Tuesday, February 3, 2015 6:36:40 AM EST, Forrest Liu wrote:
> 2015-02-03 2:40 GMT+08:00 Ed Tomlinson <edt@aei.ca>:
>> On Monday, February 2, 2015 9:39:06 AM EST, Ed Tomlinson wrote:
>>
>> Hi
>>
>> Booting a kernel with the three patches:
>> [PATCH] Btrfs: fix find_free_dev_extent() malfunction in case device tree
>> has hole ...
>
> My fault, i should test these patches before i submit these patches.
> The oops was caused by patch
> "Btrfs: btrfs_release_extent_buffer_page() didn't free pages of
> dummy extent"
>
> I will resend these patches after test on linux-3.19-rc7.
>
> Thanks
> Forrest
>
>> Anyone else?
>>
>> Thanks
>> Ed Tomlinson
>> ...
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
next prev parent reply other threads:[~2015-02-03 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 7:31 [PATCH] Btrfs: fix find_free_dev_extent() malfunction in case device tree has hole Forrest Liu
2015-02-02 14:39 ` Ed Tomlinson
2015-02-02 18:40 ` Ed Tomlinson
2015-02-03 11:36 ` Forrest Liu
2015-02-03 18:01 ` Ed Tomlinson [this message]
2015-02-04 7:14 ` Liu Bo
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=6a7eaaa1-ee4b-4c8f-905c-c9b6da9ba0b8@aei.ca \
--to=edt@aei.ca \
--cc=forrestl@synology.com \
--cc=linux-btrfs@vger.kernel.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.