-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/14/2014 01:10 AM, Daniel Golle wrote:
> 550-ubifs-symlink-xattr-support.patch contains a reference to the 
> by now obsolete config symbol CONFIG_UBIFS_FS_XATTR which leads to 
> the functionality originally added by the patch being left-out
> during compile on recent kernels. Fix this by removing the #ifdef.
> 
> Signed-off-by: Daniel Golle <[email protected]> --- 
> .../linux/generic/patches-3.14/550-ubifs-symlink-xattr-support.patch
> | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git
> a/target/linux/generic/patches-3.14/550-ubifs-symlink-xattr-support.patch
> b/target/linux/generic/patches-3.14/550-ubifs-symlink-xattr-support.patch
>
> 
index f08ec02..9ca8ac1 100644
> ---
> a/target/linux/generic/patches-3.14/550-ubifs-symlink-xattr-support.patch
>
> 
+++
b/target/linux/generic/patches-3.14/550-ubifs-symlink-xattr-support.patch

I think this does not only effect kernel 3.14 but also 3.10. I saw a
similar patch in the patches send by Belkin.

Hauke

> @@ -1,15 +1,13 @@ --- a/fs/ubifs/file.c +++ b/fs/ubifs/file.c -@@
> -1577,6 +1577,12 @@ const struct inode_operations ubifs_syml +@@
> -1577,6 +1577,10 @@ const struct inode_operations ubifs_syml 
> .follow_link = ubifs_follow_link, .setattr     = ubifs_setattr, 
> .getattr     = ubifs_getattr, -+#ifdef CONFIG_UBIFS_FS_XATTR +
> .setxattr    = ubifs_setxattr, +      .getxattr    = ubifs_getxattr, +
> .listxattr   = ubifs_listxattr, +     .removexattr =
> ubifs_removexattr, -+#endif };
> 
> const struct file_operations ubifs_file_operations = {
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTczs6AAoJEIZ0px9YPRMyhLMQAJfpXJkFDv9o7e/GpK9JIBes
iE1BSIND0ExUj8DyJSfrq01JQZlrWY9FYefS41ShipcUlzKAEKzPkzVrwzWRhLTA
BBsfXICysI3uzIEowQvt2sgNcD+P3scoJzB3muBW3AM+g1RQ/DjZpgv7hy7I09ho
o+GIQumyQFpgWPtVxE0q1daJI0DUr303a2DHnTYynaG/TMfO3maqsJPzNz5qZa2V
G8IXZ4aiPBoHK6Vwku88Wxx3x2USt68QzacoL1fAmIaYdfhTy1JjO6u1YNc6kSZR
Fo9dvwnG1xPFJLKVyWpWRa7gapzNCxt9xZXmKJbxbCexf0rvguyjGoeqvNjnUeRf
Pd/d+DW4FDDOzoNbBwwwG5rExSUPa3ExgyrRKppa+7l4JpUq+BmKdSt1Ffg6DY32
ySJyLpzJsL5xbrj92Wo3m+559jBO/4j/gqJanHA8pduJj6U7hPmZkW+Q76m0DUgn
JrXJi1Gxq5Dn5qGVa/G8k+vKIF5eF67U0+wnkOnpLqCHvbYbXSdlGmYjZhsTGGhN
rfKHdt3qhDsP9NF6B5IfsqzJlYa1P2N6Zbv6tOXC/tZsvqIfNVzJZRnKA4ZJnrvW
PCSKbl5lpQ/xtEJKNr/8ICSNEr2uO2pSPlKvKCzgUQAtsLH/vUBrhyGGdnMB+2nN
lWJWO/s5gduLTI3Oy57E
=PCNL
-----END PGP SIGNATURE-----
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to