Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+Export\s+xfs_attr_set_int

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+Export\s+xfs_attr_set_int_trans\s*$/: 12 ]

Total 12 documents matching your query.

1. [PATCH] Export xfs_attr_set_int_trans (score: 1): Author:; Date: Fri, 11 Jul 2008 15:38:14 +1000; make xfs_attr_set_int_trans non static so we can use it outside of xfs_attr.c (Needed to use it in vnodeops.c, for create+EA) Signed-off-by: Niv Sardi <xaiki@xxxxxxx> -- fs/xfs/xfs_attr.c | 2 +- fs/x; /archives/xfs/2008-07/msg00197.html (10,102 bytes)
2. Re: [PATCH] Export xfs_attr_set_int_trans (score: 1): Author:; Date: Tue, 22 Jul 2008 00:43:37 -0400; Any reason this is not merged into the previous patch?; /archives/xfs/2008-07/msg00333.html (9,413 bytes)
3. Re: [PATCH] Export xfs_attr_set_int_trans (score: 1): Author:; Date: Tue, 22 Jul 2008 16:06:55 +1000; you =) you didn't like my attr_* function to be exported, so I splitted the export out from now on. that's about it. Cheers, -- Niv Sardi; /archives/xfs/2008-07/msg00336.html (9,877 bytes)
4. Re: [PATCH] Export xfs_attr_set_int_trans (score: 1): Author:; Date: Wed, 23 Jul 2008 03:46:04 -0400; Heh, sorry. The general rule is exporting it is fine if one of the next patches uses it. That wasn't obvious when you posted the first patches, so I asked for it to be static for now.; /archives/xfs/2008-07/msg00389.html (10,344 bytes)
5. [PATCH] Export xfs_attr_set_int_trans (score: 1): Author: xxxxxx>; Date: Fri, 11 Jul 2008 15:38:14 +1000; make xfs_attr_set_int_trans non static so we can use it outside of xfs_attr.c (Needed to use it in vnodeops.c, for create+EA) Signed-off-by: Niv Sardi <xaiki@xxxxxxx> -- fs/xfs/xfs_attr.c | 2 +- fs/x; /archives/xfs/2008-07/msg00820.html (10,102 bytes)
6. Re: [PATCH] Export xfs_attr_set_int_trans (score: 1): Author: xxxxxx>; Date: Tue, 22 Jul 2008 00:43:37 -0400; Any reason this is not merged into the previous patch?; /archives/xfs/2008-07/msg00956.html (9,413 bytes)
7. Re: [PATCH] Export xfs_attr_set_int_trans (score: 1): Author: xxxxxx>; Date: Tue, 22 Jul 2008 16:06:55 +1000; you =) you didn't like my attr_* function to be exported, so I splitted the export out from now on. that's about it. Cheers, -- Niv Sardi; /archives/xfs/2008-07/msg00959.html (9,877 bytes)
8. Re: [PATCH] Export xfs_attr_set_int_trans (score: 1): Author: ivanik); Date: Wed, 23 Jul 2008 03:46:04 -0400; Heh, sorry. The general rule is exporting it is fine if one of the next patches uses it. That wasn't obvious when you posted the first patches, so I asked for it to be static for now.; /archives/xfs/2008-07/msg01012.html (10,344 bytes)
9. [PATCH] Export xfs_attr_set_int_trans (score: 1): Author: Niv Sardi <xaiki@xxxxxxx>; Date: Fri, 11 Jul 2008 15:38:14 +1000; make xfs_attr_set_int_trans non static so we can use it outside of xfs_attr.c (Needed to use it in vnodeops.c, for create+EA) Signed-off-by: Niv Sardi <xaiki@xxxxxxx> -- fs/xfs/xfs_attr.c | 2 +- fs/x; /archives/xfs/2008-07/msg01443.html (10,194 bytes)
10. Re: [PATCH] Export xfs_attr_set_int_trans (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 22 Jul 2008 00:43:37 -0400; Any reason this is not merged into the previous patch?; /archives/xfs/2008-07/msg01579.html (9,551 bytes)
11. Re: [PATCH] Export xfs_attr_set_int_trans (score: 1): Author: Niv Sardi <xaiki@xxxxxxx>; Date: Tue, 22 Jul 2008 16:06:55 +1000; you =) you didn't like my attr_* function to be exported, so I splitted the export out from now on. that's about it. Cheers, -- Niv Sardi; /archives/xfs/2008-07/msg01582.html (10,029 bytes)
12. Re: [PATCH] Export xfs_attr_set_int_trans (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 23 Jul 2008 03:46:04 -0400; Heh, sorry. The general rule is exporting it is fine if one of the next patches uses it. That wasn't obvious when you posted the first patches, so I asked for it to be static for now.; /archives/xfs/2008-07/msg01635.html (10,512 bytes)

Current List: 1 - 12
Page: [1]