Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+09\/21\]\s+implement\s+generic\s+xfs_btree

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+09\/21\]\s+implement\s+generic\s+xfs_btree_increment\s*$/: 12 ]

Total 12 documents matching your query.

1. Re: [PATCH 09/21] implement generic xfs_btree_increment (score: 1): Author: Christoph Hellwig <hch@xxxxxx>; Date: Fri, 1 Aug 2008 21:40:00 +0200; Well, all this and much more is documented at the implementation site, so I'd avoid this churn. If there are strong feelings for it I can change the prototypes. Normally I'd agree with you, but for t; /archives/xfs/2008-08/msg00009.html (9,675 bytes)
2. Re: [PATCH 09/21] implement generic xfs_btree_increment (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Sat, 2 Aug 2008 10:35:06 +1000; Not a big deal, really. I was just looking at consistency with the other prototypes around this one.... Sure, but this particular piece of code is different to wthe original btree anyway because it h; /archives/xfs/2008-08/msg00020.html (9,606 bytes)
3. Re: [PATCH 09/21] implement generic xfs_btree_increment (score: 1): Author: xx>; Date: Fri, 1 Aug 2008 21:40:00 +0200; Well, all this and much more is documented at the implementation site, so I'd avoid this churn. If there are strong feelings for it I can change the prototypes. Normally I'd agree with you, but for t; /archives/xfs/2008-08/msg00457.html (9,675 bytes)
4. Re: [PATCH 09/21] implement generic xfs_btree_increment (score: 1): Author: xx>; Date: Sat, 2 Aug 2008 10:35:06 +1000; Not a big deal, really. I was just looking at consistency with the other prototypes around this one.... Sure, but this particular piece of code is different to wthe original btree anyway because it h; /archives/xfs/2008-08/msg00468.html (9,606 bytes)
5. [PATCH 09/21] implement generic xfs_btree_increment (score: 1): Author: xxxxx>; Date: Tue, 29 Jul 2008 21:30:53 +0200; Because this is the first major generic btree routine this patch includes some infrastrucure, fistly a few routines to deal with a btree block that can be either in short or long form, and secondly x; /archives/xfs/2008-07/msg00583.html (47,384 bytes)
6. Re: [PATCH 09/21] implement generic xfs_btree_increment (score: 1): Author: xxxxx>; Date: Wed, 30 Jul 2008 12:06:45 +1000; ..... I think for these interfaces it woul dbe better to include variable names in the prototypes. i.e.: int xfs_btree_increment(struct xfs_btree_cur *cur, int level, int *stat); Can kill the else th; /archives/xfs/2008-07/msg00598.html (15,700 bytes)
7. [PATCH 09/21] implement generic xfs_btree_increment (score: 1): Author: <hch@xxxxxx>; Date: Tue, 29 Jul 2008 21:30:53 +0200; Because this is the first major generic btree routine this patch includes some infrastrucure, fistly a few routines to deal with a btree block that can be either in short or long form, and secondly x; /archives/xfs/2008-07/msg01206.html (47,384 bytes)
8. Re: [PATCH 09/21] implement generic xfs_btree_increment (score: 1): Author: xxxxxxxxxxxx>; Date: Wed, 30 Jul 2008 12:06:45 +1000; ..... I think for these interfaces it woul dbe better to include variable names in the prototypes. i.e.: int xfs_btree_increment(struct xfs_btree_cur *cur, int level, int *stat); Can kill the else th; /archives/xfs/2008-07/msg01221.html (15,700 bytes)
9. Re: [PATCH 09/21] implement generic xfs_btree_increment (score: 1): Author: Christoph Hellwig <hch@xxxxxx>; Date: Fri, 1 Aug 2008 21:40:00 +0200; Well, all this and much more is documented at the implementation site, so I'd avoid this churn. If there are strong feelings for it I can change the prototypes. Normally I'd agree with you, but for t; /archives/xfs/2008-08/msg00905.html (9,849 bytes)
10. Re: [PATCH 09/21] implement generic xfs_btree_increment (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Sat, 2 Aug 2008 10:35:06 +1000; Not a big deal, really. I was just looking at consistency with the other prototypes around this one.... Sure, but this particular piece of code is different to wthe original btree anyway because it h; /archives/xfs/2008-08/msg00916.html (9,780 bytes)
11. [PATCH 09/21] implement generic xfs_btree_increment (score: 1): Author: Christoph Hellwig <hch@xxxxxx>; Date: Tue, 29 Jul 2008 21:30:53 +0200; Because this is the first major generic btree routine this patch includes some infrastrucure, fistly a few routines to deal with a btree block that can be either in short or long form, and secondly x; /archives/xfs/2008-07/msg01829.html (47,384 bytes)
12. Re: [PATCH 09/21] implement generic xfs_btree_increment (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Wed, 30 Jul 2008 12:06:45 +1000; ..... I think for these interfaces it woul dbe better to include variable names in the prototypes. i.e.: int xfs_btree_increment(struct xfs_btree_cur *cur, int level, int *stat); Can kill the else th; /archives/xfs/2008-07/msg01844.html (15,760 bytes)

Current List: 1 - 12
Page: [1]