Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+1\/4\]\s+xfs\:\s+make\s+i_flags\s+and\s+unsigned\s+long\s*$/: 5 ]

Total 5 documents matching your query.

1. [PATCH 1/4] xfs: make i_flags and unsigned long (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 18 Oct 2011 16:13:05 -0400
To be used for bit wakeup i_flags needs to be an unsigned long or we'll run into trouble on big endian systems. Beause of the 1-byte i_update field right after it this actually causes a fairly large
/archives/xfs/2011-10/msg00363.html (8,387 bytes)

2. Re: [PATCH 1/4] xfs: make i_flags and unsigned long (score: 1)
Author: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 19 Oct 2011 11:30:47 +1100
You could always make the i_update_core boolean a flag bit, and that growth will also go away. Regardless: Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx> -- Dave Chinner david@xxxxxxxxxxxxx
/archives/xfs/2011-10/msg00368.html (9,045 bytes)

3. Re: [PATCH 1/4] xfs: make i_flags and unsigned long (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 19 Oct 2011 04:57:57 -0400
I could. Then again I plan to kill it for 3.3, so re-arranging the deck charis now might not be all that useful.
/archives/xfs/2011-10/msg00372.html (9,770 bytes)

4. [PATCH 1/4] xfs: make i_flags and unsigned long (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 19 Oct 2011 14:23:44 -0400
To be used for bit wakeup i_flags needs to be an unsigned long or we'll run into trouble on big endian systems. Beause of the 1-byte i_update field right after it this actually causes a fairly large
/archives/xfs/2011-10/msg00394.html (8,442 bytes)

5. Re: [PATCH 1/4] xfs: make i_flags and unsigned long (score: 1)
Author: Alex Elder <aelder@xxxxxxx>
Date: Wed, 26 Oct 2011 16:07:12 -0500
Looks fine. Reviewed-by: Alex Elder <aelder@xxxxxxx>
/archives/xfs/2011-10/msg00466.html (9,025 bytes)


This search system is powered by Namazu