From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Yinghai Lu <yhlu.kernel@gmail.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: [RFC] improve alignf() calling convention in allocate_resource()
Date: Fri, 1 Jan 2010 17:38:11 +0100 [thread overview]
Message-ID: <20100101163811.GA8124@comet.dominikbrodowski.net> (raw)
In-Reply-To: <alpine.LFD.2.00.0912210801260.21722@localhost.localdomain>
On Mon, Dec 21, 2009 at 08:03:02AM -0800, Linus Torvalds wrote:
> > What about taking my patch for 2.6.33, and deferring the change to the
> > calling convention to the 2.6.34 merge window? (I'll try to cook something
> > up and get it into linux-next during the next few weeks).
Based on the previous discussion, I've prepared two patches which change the
calling convention of alignf() to
resource_size_t (*alignf)(void *data,
const struct resource *new,
resource_size_t size,
resource_size_t align)
. Any feedback is welcome.
arch/alpha/kernel/pci.c | 6 +++---
arch/arm/kernel/bios32.c | 8 +++++---
arch/cris/arch-v32/drivers/pci/bios.c | 16 +++++++---------
arch/frv/mb93090-mb00/pci-frv.c | 16 +++++++---------
arch/ia64/pci/pci.c | 5 +++--
arch/mips/pci/pci.c | 6 +++---
arch/mips/pmc-sierra/yosemite/ht.c | 10 +++++-----
arch/mn10300/unit-asb2305/pci-asb2305.c | 16 +++++++---------
arch/parisc/kernel/pci.c | 10 +++++-----
arch/powerpc/kernel/pci-common.c | 13 ++++++-------
arch/sh/drivers/pci/pci.c | 6 +++---
arch/sparc/kernel/pci.c | 5 +++--
arch/sparc/kernel/pcic.c | 5 +++--
arch/x86/pci/i386.c | 14 ++++++--------
arch/xtensa/kernel/pci.c | 15 +++++++--------
drivers/pci/bus.c | 6 ++++--
drivers/pcmcia/rsrc_mgr.c | 13 +++++++------
drivers/pcmcia/rsrc_nonstatic.c | 22 ++++++++++++----------
include/linux/ioport.h | 6 ++++--
include/linux/pci.h | 9 ++++++---
kernel/resource.c | 14 +++++++++-----
21 files changed, 115 insertions(+), 106 deletions(-)
Best,
Dominik
next parent reply other threads:[~2010-01-01 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091220095001.GA6029@comet.dominikbrodowski.net>
[not found] ` <alpine.LFD.2.00.0912201026570.3712@localhost.localdomain>
[not found] ` <20091221084031.GB1648@isilmar.linta.de>
[not found] ` <alpine.LFD.2.00.0912210801260.21722@localhost.localdomain>
2010-01-01 16:38 ` Dominik Brodowski [this message]
2010-01-01 16:38 ` [RFC] improve alignf() calling convention in allocate_resource() Dominik Brodowski
2010-01-01 16:40 ` [PATCH 1/2] resource: align functions now return start of resource Dominik Brodowski
2010-01-01 16:40 ` Dominik Brodowski
2010-01-01 22:12 ` Yinghai Lu
2010-01-03 16:30 ` Dominik Brodowski
2010-01-03 16:30 ` Dominik Brodowski
2010-01-15 18:23 ` Jesse Barnes
2010-01-15 18:23 ` Jesse Barnes
2010-01-01 16:40 ` [PATCH 2/2] resource: mark struct resource as const Dominik Brodowski
2010-01-01 16:40 ` Dominik Brodowski
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=20100101163811.GA8124@comet.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=bjorn.helgaas@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yhlu.kernel@gmail.com \
/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).