Re: [patch 1/3] add the fsblock layer

> Hmm, could define a macro DECLARE_ATOMIC_BITMAP(maxbit) that expands to the smallest
> possible type for each architecture. And a couple of ugly casts for set_bit et.al.
> but those could be also hidden in macros. Should be relatively easy to do.

or make a "smallbit" type that is small/supported, so 64 bit if 32 bit
isn't supported, otherwise 32


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch 1/3] add the fsblock layer
    • From: Andi Kleen <[email protected]>

• References:
  • [RFC] fsblock
    • From: Nick Piggin <[email protected]>
  • [patch 1/3] add the fsblock layer
    • From: Nick Piggin <[email protected]>
  • Re: [patch 1/3] add the fsblock layer
    • From: Andi Kleen <[email protected]>

• Prev by Date: Re: DCCP: 2.6.22-rc5-git8 compile warning
• Next by Date: Re: [RC][PATCH -mm] PM: Prevent frozen user mode helpers from failing the freezing of tasks
• Previous by thread: Re: [patch 1/3] add the fsblock layer
• Next by thread: Re: [patch 1/3] add the fsblock layer
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]