Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+07\/16\]\s+xfs\:\s+remove\s+XFS_DQ

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+07\/16\]\s+xfs\:\s+remove\s+XFS_DQ_INACTIVE\s*$/: 5 ]

Total 5 documents matching your query.

1. [PATCH 07/16] xfs: remove XFS_DQ_INACTIVE (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Mon, 28 Nov 2011 03:27:29 -0500; Free dquots when purging them during umount instead of keeping them around on the freelist in a degraded state. The out of order locking in xfs_qm_dqpurge will be removed again later in this series.; /archives/xfs/2011-11/msg00541.html (16,209 bytes)
2. Re: [PATCH 07/16] xfs: remove XFS_DQ_INACTIVE (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Mon, 5 Dec 2011 15:23:51 +1100; While there, you may as well make that a "return 0;" Don't we still need that mutex_destroy() call there? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx; /archives/xfs/2011-12/msg00063.html (9,138 bytes)
3. Re: [PATCH 07/16] xfs: remove XFS_DQ_INACTIVE (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Mon, 5 Dec 2011 03:37:41 -0500; Indeed. We never needed it - Linux does an implicit mutex_destory when freeing memory containing a mutex.; /archives/xfs/2011-12/msg00078.html (8,243 bytes)
4. Re: [PATCH 07/16] xfs: remove XFS_DQ_INACTIVE (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 6 Dec 2011 09:43:50 -0500; Does this count as a revied-by now?; /archives/xfs/2011-12/msg00097.html (8,767 bytes)
5. Re: [PATCH 07/16] xfs: remove XFS_DQ_INACTIVE (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Wed, 7 Dec 2011 07:34:32 +1100; Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx> -- Dave Chinner david@xxxxxxxxxxxxx; /archives/xfs/2011-12/msg00114.html (9,244 bytes)

Current List: 1 - 5
Page: [1]