Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+3\/9\]\s+xfs\:\s+add\s+discontiguous\s+buffer\s+map\s+interface\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+3\/9\]\s+xfs\:\s+add\s+discontiguous\s+buffer\s+map\s+interface\s*$/: 2 ]

Total 2 documents matching your query.

1. [PATCH 3/9] xfs: add discontiguous buffer map interface (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Fri, 8 Jun 2012 15:38:28 +1000; With the internal interfaces supporting discontiguous buffer maps, add external lookup, read and get interfaces so they can start to be used. Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx> -- fs/x; /archives/xfs/2012-06/msg00091.html (13,740 bytes)
2. Re: [PATCH 3/9] xfs: add discontiguous buffer map interface (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 20 Jun 2012 02:53:23 -0400; I'm not a big fan of creative macro use, but with the amount of copies of these line why not add a: struct xfs_buf_map (map) = { .bm_bn = (blkno), .bm_len = (numblk) }; Otherwise looks good, Reviewe; /archives/xfs/2012-06/msg00317.html (9,694 bytes)

Current List: 1 - 2
Page: [1]