Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Review\:\s+clean\s+up\s+inode\s+i

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Review\:\s+clean\s+up\s+inode\s+i_flags\s+handling\s*$/: 6 ]

Total 6 documents matching your query.

1. Review: clean up inode i_flags handling (score: 1): Author: David Chinner <dgc@xxxxxxx>; Date: Tue, 3 Oct 2006 15:13:25 +1000; As a followup to the recent inode i_flags modification and the introduction of the i_flags_lock, introduce a set of wrapper functions for setting, clearing and testing flags in the i_flags field and; /archives/xfs/2006-10/msg00014.html (17,378 bytes)
2. Re: Review: clean up inode i_flags handling (score: 1): Author: Nathan Scott <nscott@xxxxxxxxxx>; Date: Wed, 04 Oct 2006 08:26:13 +1000; This part seems like overkill, I'd just do that inline like the clear variant, since its just one instruction ... +static inline void +__xfs_iflags_set(xfs_inode_t *ip, unsigned short flags) +{ + ip-; /archives/xfs/2006-10/msg00029.html (7,938 bytes)
3. Re: Review: clean up inode i_flags handling (score: 1): Author: Nathan Scott <nscott@xxxxxxxxxx>; Date: Wed, 04 Oct 2006 09:58:50 +1000; ..but I guess you did it for consistency, as that one instruction is otherwise going to have to be open coded in a few places ... *shrug* looks good to me either way. cheers. -- Nathan; /archives/xfs/2006-10/msg00031.html (8,053 bytes)
4. ce (score: 1): Author: xxxxxxxxxxxxxxxx>; Date: Tue, 3 Oct 2006 15:13:25 +1000; (; /archives/xfs/2006-10/msg00391.html (17,378 bytes)
5. to radix trees (score: 1): Author: >; Date: Wed, 04 Oct 2006 08:26:13 +1000; ha; /archives/xfs/2006-10/msg00406.html (7,938 bytes)
6. ranscript.html .pif Infected with Win32.Mydoom.m (score: 1): Author: @xxxxxxxxxx>; Date: Wed, 04 Oct 2006 09:58:50 +1000; ffering a severe case of RSI problems. Please forgive slow and terse replies as I deal with this. Thank you for your patienc; /archives/xfs/2006-10/msg00408.html (8,053 bytes)

Current List: 1 - 6
Page: [1]