On Tue, 2 May 2006 16:42:16 -0400 Vivek Goyal <[email protected]> wrote: > > Yes, it would need to to be a new type - resource_addr_t, perhaps. > > > > How about "res_sz_t". resource_size_t, please. > "resource_addr_t" probably is not a very appropriate > keyword as at lots of places we also need to represent size and alignment > with this typedef. OK. - 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/
- References:
- [PATCH] catch valid mem range at onlining memory
- From: KAMEZAWA Hiroyuki <[email protected]>
- Re: [PATCH] catch valid mem range at onlining memory
- From: Andrew Morton <[email protected]>
- Re: [PATCH] catch valid mem range at onlining memory
- From: Greg KH <[email protected]>
- Re: [PATCH] catch valid mem range at onlining memory
- From: Andrew Morton <[email protected]>
- Re: [PATCH] catch valid mem range at onlining memory
- From: Greg KH <[email protected]>
- Re: [PATCH] catch valid mem range at onlining memory
- From: Vivek Goyal <[email protected]>
- Re: [PATCH] catch valid mem range at onlining memory
- From: Andrew Morton <[email protected]>
- Re: [PATCH] catch valid mem range at onlining memory
- From: Vivek Goyal <[email protected]>
- [PATCH] catch valid mem range at onlining memory
- Prev by Date: Re: Add a "enable" sysfs attribute to the pci devices to allow userspace (Xorg) to enable devices without doing foul direct access
- Next by Date: Re: [ck] 2.6.16-ck9
- Previous by thread: Re: [PATCH] catch valid mem range at onlining memory
- Next by thread: Re: [PATCH] catch valid mem range at onlining memory
- Index(es):
 |