Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"

> One of the possible solutions to this problem is that expand the size
> of "start" and "end" to "unsigned long long". But whole of the PCI and
> driver code has been written assuming start and end to be unsigned long
> and compiler starts throwing warnings. 


please use dma_addr_t then instead of unsigned long long

this is the right size on all platforms afaik (could a ppc64 person
verify this?> ;)

-
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: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
  - From: "David S. Miller" <[email protected]>
- Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
  - From: Kumar Gala <[email protected]>

References:
- [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
  - From: Vivek Goyal <[email protected]>

Prev by Date: Re: [RFC, PATCH 0/24] VMI i386 Linux virtualization interface proposal
Next by Date: Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
Previous by thread: Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
Next by thread: Re: [RFC][PATCH] Expanding the size of "start" and "end" field in "struct resource"
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]