| To: | Bjorn Helgaas <bjorn.helgaas@hp.com> |
|---|---|
| Subject: | Re: [patch 1/2] rtc: release correct region in error path |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Wed, 24 Oct 2007 16:12:50 +0100 |
| Cc: | Alessandro Zummo <a.zummo@towertech.it>, Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org, linux-mips@linux-mips.org |
| In-reply-to: | <20071023205515.406778977@ldl.fc.hp.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20071023204843.442608289@ldl.fc.hp.com> <20071023205515.406778977@ldl.fc.hp.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.14 (2007-02-12) |
On Tue, Oct 23, 2007 at 02:48:44PM -0600, Bjorn Helgaas wrote: > Subject: [patch 1/2] rtc: release correct region in error path > > The misc_register() error path always released an I/O port region, > even if the region was memory-mapped (only mips uses memory-mapped RTC, > as far as I can see). Well, MIPS just like other sane architectures has no concept of ioports. So if there ever is something that's called an ioport on MIPS then it's really a memory location in a memory address range where other PCish devices are living, too. So typically those memory addresses are translated to an actual ioport access by a PCI bridge. There are a few systems where this concept just apply easily such as DECstations, so there we simply claim the device such as the RTC in this case is memory mapped. Anway: Acked-by: Ralf Baechle <ralf@linux-mips.org> Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] cleanup tx39/tx49 setup code, Atsushi Nemoto |
|---|---|
| Next by Date: | [PATCH] txx9tmr clockevent/clocksource driver (take 2), Atsushi Nemoto |
| Previous by Thread: | [patch 1/2] rtc: release correct region in error path, Bjorn Helgaas |
| Next by Thread: | 2.6.23-rc1 ..., Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |