From: Cyrill Gorcunov <gorcunov@gmail.com>
To: linux-kernel@vger.kernel.org, davem@davemloft.net,
bryan.wu@analog.com, hskinnemoen@atmel.co, dhowells@redhat.com
Subject: [patch 0/4] cleanup - use _AC macro to define PAGE_SIZE
Date: Sun, 03 Feb 2008 14:22:17 +0300 [thread overview]
Message-ID: <47a5a65d.03eb300a.07b8.130e@mx.google.com> (raw)
This patch series removes code duplication for PAGE_SIZE
definition on various architectures.
Please review. Any comments are welcome. *UNTESTED*
Statistics:
asm-avr32/page.h | 8 +++-----
asm-blackfin/page.h | 8 +++-----
asm-frv/mem-layout.h | 10 +++-------
asm-sparc/page.h | 11 ++++-------
4 files changed, 13 insertions(+), 24 deletions(-)
- Cyrill -
--
next reply other threads:[~2008-02-03 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 11:22 Cyrill Gorcunov [this message]
2008-02-03 12:22 ` [patch 0/4] cleanup - use _AC macro to define PAGE_SIZE Sam Ravnborg
2008-02-03 12:40 ` Cyrill Gorcunov
2008-02-03 13:07 ` Cyrill Gorcunov
2008-02-04 20:01 ` Mike Frysinger
2008-02-04 20:28 ` Sam Ravnborg
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=47a5a65d.03eb300a.07b8.130e@mx.google.com \
--to=gorcunov@gmail.com \
--cc=bryan.wu@analog.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=hskinnemoen@atmel.co \
--cc=linux-kernel@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