Re: [PATCH] arch/xx/pci: remap_pfn_range -> io_remap_pfn_range

Quoting r. Greg KH <[email protected]>:
> Subject: Re: [PATCH] arch/xx/pci: remap_pfn_range -> io_remap_pfn_range
> 
> On Tue, Jul 26, 2005 at 01:32:00AM +0300, Michael S. Tsirkin wrote:
> > Greg, Martin, does the following make sense?
> > If it does, should other architectures be updated as well?
> > 
> Hm, you do realize that io_remap_pfn_range() is the same thing as
> remap_pfn_range() on i386, right?
> 
> So, why would this patch change anything?
> 
> thanks,
> 
> greg k-h
> 

It doesnt change any behaviour.
Its a style issue I'm trying to fix: even in arch specific code, isnt it better
to use a generic io_remap_pfn_range to map PCI memory?

-- 
MST
-
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] arch/xx/pci: remap_pfn_range -> io_remap_pfn_range
    • From: Greg KH <[email protected]>

• References:
  • [PATCH] arch/xx/pci: remap_pfn_range -> io_remap_pfn_range
    • From: "Michael S. Tsirkin" <[email protected]>
  • Re: [PATCH] arch/xx/pci: remap_pfn_range -> io_remap_pfn_range
    • From: Greg KH <[email protected]>

• Prev by Date: Re: system freezes for 0.2 to 0.5 seconds when reading /proc/acpi/thermal_zone/THRM/temperature
• Next by Date: [PATCH] Disable the debug.exception-trace sysctl by default
• Previous by thread: Re: [openib-general] Re: [PATCH] arch/xx/pci: remap_pfn_range -> io_remap_pfn_range
• Next by thread: Re: [PATCH] arch/xx/pci: remap_pfn_range -> io_remap_pfn_range
• Index(es):
  • Date
  • Thread

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