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@xxxxxx>:
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
