From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: linux-ide@vger.kernel.org, alan@lxorguk.ukuu.org.uk,
alan@redhat.com, htejun@gmail.com
Subject: Re: [patch 10/11] iomap: sort out the broken address reporting caused by the iomap layer
Date: Fri, 20 Jul 2007 08:11:53 -0400 [thread overview]
Message-ID: <46A0A689.9020800@garzik.org> (raw)
In-Reply-To: <200707091846.l69IkNop001393@imap1.linux-foundation.org>
akpm@linux-foundation.org wrote:
> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
>
> Add an iomap_name() function which translates an I/O map into a string to
> print.
>
> Use it for the Libata layer
>
> For now we use 0xXXXX for I/O and 0xXXXXXXXX for MMIO. I'm assuming that
> eventually some other platforms will want to use their own iomap_name() and
> we can add ARCH_HAVE_IOMAP_NAME later as such a platform needs it.
>
> Signed-off-by: Alan Cox <alan@redhat.com>
> Cc: Jeff Garzik <jeff@garzik.org>
> Cc: Tejun Heo <htejun@gmail.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> include/asm-generic/iomap.h | 5 +++++
> lib/iomap.c | 12 ++++++++++++
> 2 files changed, 17 insertions(+)
>
> diff -puN include/asm-generic/iomap.h~iomap-sort-out-the-broken-address-reporting-caused-by-the-iomap-layer include/asm-generic/iomap.h
> --- a/include/asm-generic/iomap.h~iomap-sort-out-the-broken-address-reporting-caused-by-the-iomap-layer
> +++ a/include/asm-generic/iomap.h
> @@ -65,4 +65,9 @@ struct pci_dev;
> extern void __iomem *pci_iomap(struct pci_dev *dev, int bar, unsigned long max);
> extern void pci_iounmap(struct pci_dev *dev, void __iomem *);
>
> +/* Convert an iomap to text for this platform */
> +extern char *iomap_name(void __iomem *addr, char *buf, size_t len);
> +#define IOMAP_NAMELEN 12
this will truncate on 64-bit addresses
otherwise OK
next prev parent reply other threads:[~2007-07-20 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 18:46 [patch 10/11] iomap: sort out the broken address reporting caused by the iomap layer akpm
2007-07-20 12:11 ` Jeff Garzik [this message]
2007-07-20 12:22 ` Alan Cox
2007-07-20 12:24 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46A0A689.9020800@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).