From: Andrew Morton <akpm@osdl.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Valdis.Kletnieks@vt.edu, greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.11-rc5-mm1
Date: Tue, 1 Mar 2005 12:42:11 -0800 [thread overview]
Message-ID: <20050301124211.01375439.akpm@osdl.org> (raw)
In-Reply-To: <20050301152735.B1940@flint.arm.linux.org.uk>
Russell King <rmk+lkml@arm.linux.org.uk> wrote:
>
> On Tue, Mar 01, 2005 at 10:18:56AM -0500, Valdis.Kletnieks@vt.edu wrote:
> > On Tue, 01 Mar 2005 13:55:29 GMT, Russell King said:
> > > The PCI updates change the prototype of a helper function for
> > > pci_bus_alloc_resource(), but don't touch the actual helper function
> > > in PCMCIA.
> >
> > That explains the warning messages that gcc was tossing, which I suspected was
> > involved...
> >
> > > This means that the PCI update is actually broken - if it's merged as
> > > is into Linus' tree, PCMCIA will break there as well.
> >
> > Is the patch made to PCI actually incorrect, or is the proper way to do this
> > to propagate the changes into the relevant PCMCIA code?
>
> PCI has been updated to accept 64-bit resources, but the PCMCIA code
> has been missed. So the correct fix is to propagate the changes where
> necessary into the PCMCIA code.
hmm, I missed that. That's the price of two screenfuls of fscking compile
warnings.
> The minimalist solution is to fix up the PCMCIA alignment functions.
Greg's dropping the 64-bit-resource patch for now.
next prev parent reply other threads:[~2005-03-01 20:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 9:27 2.6.11-rc5-mm1 Andrew Morton
2005-03-01 13:36 ` 2.6.11-rc5-mm1 Valdis.Kletnieks
2005-03-01 13:55 ` 2.6.11-rc5-mm1 Russell King
2005-03-01 15:18 ` 2.6.11-rc5-mm1 Valdis.Kletnieks
2005-03-01 15:27 ` 2.6.11-rc5-mm1 Russell King
2005-03-01 20:42 ` Andrew Morton [this message]
2005-03-01 20:45 ` 2.6.11-rc5-mm1 Greg KH
2005-03-01 13:53 ` 2.6.11-rc5-mm1 Mathieu Segaud
2005-03-01 14:00 ` 2.6.11-rc5-mm1 Mathieu Segaud
2005-03-01 14:06 ` 2.6.11-rc5-mm1 Mathieu Segaud
2005-03-01 15:06 ` 2.6.11-rc5-mm1 Edward Shishkin
2005-03-01 15:53 ` 2.6.11-rc5-mm1 (compile stats) John Cherry
2005-03-01 17:40 ` 2.6.11-rc5-mm1 Aurélien Francillon
2005-03-02 8:53 ` 2.6.11-rc5-mm1 Andrew Morton
2005-03-02 15:45 ` 2.6.11-rc5-mm1 Andreas Gruenbacher
2005-03-03 11:01 ` 2.6.11-rc5-mm1 Aurélien Francillon
2005-03-01 20:16 ` 2.6.11-rc5-mm1 Adrian Bunk
2005-03-01 21:58 ` 2.6.11-rc5-mm1 Andrew Morton
2005-03-01 21:49 ` 2.6.11-rc5-mm1 Chris Wright
2005-03-01 22:08 ` 2.6.11-rc5-mm1 Andrew Morton
2005-03-03 8:04 ` 2.6.11-rc5-mm1 Jeff Dike
2005-03-03 16:21 ` 2.6.11-rc5-mm1 Chris Wright
2005-03-03 19:25 ` 2.6.11-rc5-mm1 Jeff Dike
2005-03-03 19:14 ` 2.6.11-rc5-mm1 Chris Wright
2005-03-04 11:01 ` 2.6.11-rc5-mm1 zwx
2005-03-01 23:43 ` [2.6.11-rc5-mm1 patch] reiser4 Kconfig help cleanup Adrian Bunk
2005-03-02 9:01 ` Jes Sorensen
2005-03-02 9:14 ` Andrew Morton
2005-03-02 14:29 ` Nikita Danilov
2005-03-02 14:40 ` [2.6.11-rc5-mm1 patch] reiser4 cleanup (PG_arch_1) Vladimir Saveliev
2005-03-03 13:17 ` [2.6.11-rc5-mm1 patch] fs/reiser4/: possible cleanups Adrian Bunk
2005-03-03 13:22 ` [2.6.11-rc5-mm1 patch] drivers/acpi/pcc_acpi.c: section fixes Adrian Bunk
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=20050301124211.01375439.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®