Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*suse\s+xfs\s+patches\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*suse\s+xfs\s+patches\s*$/: 3 ]

Total 3 documents matching your query.

1. suse xfs patches (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 14 Jun 2011 16:12:38 -0400; Hi Neil, hi Goldwyn, if you find issue with XFS and commit local patches to the SLES tree it would be very much appreciated if you could actually send them upstream, including an explanation of what; /archives/xfs/2011-06/msg00207.html (6,729 bytes)
2. Re: suse xfs patches (score: 1): Author: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>; Date: Tue, 14 Jun 2011 17:05:50 -0500; Yes sure. I suppose you are refering to the patch attached. I did not send it upstream because the upstream code had taken a different approach and the patch was relevant to the SLES kernel tree only; /archives/xfs/2011-06/msg00210.html (7,550 bytes)
3. Re: suse xfs patches (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Thu, 16 Jun 2011 11:09:41 -0400; That, and "XFS: force log before waiting for a pinned buffer". They look similar, but different enough from things that we have in mainline that make me really curious if you a) were hitting the same; /archives/xfs/2011-06/msg00226.html (8,748 bytes)

Current List: 1 - 3
Page: [1]