Re: 2.6.19 -mm merge plans

introduce-config_zone_dma.patch
optional-zone_dma-in-the-vm.patch
optional-zone_dma-in-the-vm-tidy.patch
optional-zone_dma-for-i386.patch
optional-zone_dma-for-x86_64.patch
optional-zone_dma-for-ia64.patch
remove-zone_dma-remains-from-parisc.patch
remove-zone_dma-remains-from-sh-sh64.patch

Would it not make sense to define what ZONE_DMA actually means
consistently before trying to change it? The current mess across
different architectures seems like a disaster area to me.

What DOES requesting ZONE_DMA from a driver actually mean?

M.
-
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: 2.6.19 -mm merge plans
    • From: Christoph Lameter <[email protected]>
  • ZONE_DMA (was: Re: 2.6.19 -mm merge plans)
    • From: Andrew Morton <[email protected]>

• References:
  • 2.6.19 -mm merge plans
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: [ckrm-tech] [patch00/05]: Containers(V2)- Introduction
• Next by Date: Re: [ckrm-tech] [patch00/05]: Containers(V2)- Introduction
• Previous by thread: Re: Autofs4 breakage (was 2.6.19 -mm merge plans)
• Next by thread: ZONE_DMA (was: Re: 2.6.19 -mm merge plans)
• 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]