linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] Cleanup of mach/io.h
Date: Wed, 23 Jun 2010 19:52:12 +0800	[thread overview]
Message-ID: <1277293938-25804-1-git-send-email-eric.y.miao@gmail.com> (raw)

Some definitions can be made common, like IO_SPACE_LIMIT, some can
be removed, e.g. __mem_isa(), and some can be made into a machine
specific call, e.g. arch_adjust_zones()

Many mach/io.h can actually be safely removed, except for the
following definitions:

	__io()

and
	__arch_ioremap(), __arch_iounmap() and so on

__io() in the end can be made generic into something like:

#define __io(x)		((x) - physical_address_of_IO_space +
			       virtual_base)

and __arch_ioremap(), __arch_iounmap() made into machine specific
function (again?)

             reply	other threads:[~2010-06-23 11:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 11:52 Eric Miao [this message]
2010-06-23 11:52 ` [PATCH 1/6] [ARM] Make common definition for IO_SPACE_LIMIT Eric Miao
2010-06-23 19:48   ` Russell King - ARM Linux
2010-06-23 11:52 ` [PATCH 2/6] [ARM] footbridge: remove the useless definition of __mem_pci() Eric Miao
2010-06-23 11:52 ` [PATCH 3/6] [ARM] Make __mem_pci() common to all ARM sub-architectures Eric Miao
2010-06-23 19:51   ` Russell King - ARM Linux
2010-06-23 11:52 ` [PATCH 4/6] [ARM] Remove useless __mem_isa() definitions Eric Miao
2010-06-23 11:52 ` [PATCH 5/6] [ARM] shmobile: change __io() definition to use __typesafe_io() Eric Miao
2010-06-23 11:59   ` Eric Miao
2010-06-23 11:52 ` [PATCH 6/6] [ARM] Introduce common definition for __io() Eric Miao
2010-06-23 19:54   ` Russell King - ARM Linux
2010-06-25  7:35     ` kprobe bug Bin Yang
2010-06-25 20:49       ` Nicolas Pitre
2010-06-28  2:27         ` Bin Yang
2010-06-28 15:08           ` Nicolas Pitre

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=1277293938-25804-1-git-send-email-eric.y.miao@gmail.com \
    --to=eric.y.miao@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).