Re: [PATCH 10/16] udf: create common function for changing free space counter



On Sat 12-01-08 14:13:31, Marcin Slusarz wrote:
On Fri, Jan 11, 2008 at 12:24:49AM +0100, Jan Kara wrote:
On Thu 10-01-08 23:06:26, marcin.slusarz@xxxxxxxxx wrote:
Signed-off-by: Marcin Slusarz <marcin.slusarz@xxxxxxxxx>
CC: Jan Kara <jack@xxxxxxx>
CC: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Just two minor comment...

---
fs/udf/balloc.c | 49 ++++++++++++++++++++-----------------------------
1 files changed, 20 insertions(+), 29 deletions(-)

diff --git a/fs/udf/balloc.c b/fs/udf/balloc.c
index dc9f8a9..78dbf1d 100644
--- a/fs/udf/balloc.c
+++ b/fs/udf/balloc.c
@@ -140,6 +140,20 @@ static inline int load_block_bitmap(struct super_block *sb,
return slot;
}

+static bool udf_inc_free_space(struct udf_sb_info *sbi,
Maybe because you use the function for both increasing and decreasing
free space, you could call is udf_add_free_space?
Ok. Done.


+ u16 partition, u32 cnt)
+{
+ struct logicalVolIntegrityDesc *lvid;
+
+ if (sbi->s_lvid_bh)
+ return false;
+
+ lvid = (struct logicalVolIntegrityDesc *)sbi->s_lvid_bh->b_data;
+ lvid->freeSpaceTable[partition] = cpu_to_le32(le32_to_cpu(
+ lvid->freeSpaceTable[partition]) + cnt);
I think macro like le32_add_cpu() just went into the kernel so you could
use that...
I didn't want to rely on too many patches, so I intentionally left it.
I'll convert it together with other le*_add_cpu changes.
OK, fair enough.

Can you ack this patch with udf_inc_free_space rename?
Yes.
Acked-by: Jan Kara <jack@xxxxxxx>

Honza

--
Jan Kara <jack@xxxxxxx>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: 2.6.26-rt1
    ... The merge was mostly done by Steven Rostedt, I just fixed it up, added ... so I dropped Peter's cpu-hotplug patches ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • Re: git trees which are not yet in linux-next
    ... Heh, no, but I did read somewhere that you're only supposed to put patches ... after enough exposure they graduate into or. ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • Re: [PATCH] sound/ad1848: fix printk format
    ... Some patches are really ... worth to be in 2.6.24. ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • RE: [patch 00/32] 2.6.20-stable review
    ... This is the start of the stable review cycle for the ... These patches are sent out with a number of different people on the ... Please read the FAQ at http://www.tux.org/lkml/ ... More majordomo info at http://vger.kernel.org/majordomo-info.html ...
    (Linux-Kernel)
  • Re: 2.6.25-rc5-mm1: NO_HZ=Y && PREEMPT_RCU=Y fails to build
    ... I would suspect these patches: ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)