From: Andrew Morton <akpm@osdl.org>
To: Alexey Dobriyan <adobriyan@mail.ru>
Cc: wli@holomorphy.com, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sparc: fix compile failure ("struct resource" related)
Date: Tue, 1 Mar 2005 13:44:40 -0800 [thread overview]
Message-ID: <20050301134440.05ae1152.akpm@osdl.org> (raw)
In-Reply-To: <200503012129.11840.adobriyan@mail.ru>
Alexey Dobriyan <adobriyan@mail.ru> wrote:
>
> Signed-off-by: Alexey Dobriyan <adobriyan@mail.ru>
Thanks. Many of these fixups are due to a 64-bit-resource patch in Greg's
bk-pci tree which he has now reverted. That being said:
- That patch will come back sometime
- Fixes like the below make sense anyway and can be merged any time.
- All the fixes which were only applicable when the 64-bit-resource patch
is present have been sent to Greg for when that patch reemerges.
> --- linux-2.6.11-rc5-mm1/arch/sparc/kernel/ioport.c.orig 2005-03-01 21:11:30.000000000 +0200
> +++ linux-2.6.11-rc5-mm1/arch/sparc/kernel/ioport.c 2005-03-01 21:12:48.000000000 +0200
> @@ -54,11 +54,11 @@ static void _sparc_free_io(struct resour
>
> /* This points to the next to use virtual memory for DVMA mappings */
> static struct resource _sparc_dvma = {
> - "sparc_dvma", DVMA_VADDR, DVMA_END - 1
> + .name = "sparc_dvma", .start = DVMA_VADDR, .end = DVMA_END - 1
> };
> /* This points to the start of I/O mappings, cluable from outside. */
> /*ext*/ struct resource sparc_iomap = {
> - "sparc_iomap", IOBASE_VADDR, IOBASE_END - 1
> + .name = "sparc_iomap", .start = IOBASE_VADDR, .end = IOBASE_END - 1
> };
>
> /*
next parent reply other threads:[~2005-03-01 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200503012129.11840.adobriyan@mail.ru>
2005-03-01 21:44 ` Andrew Morton [this message]
2005-03-03 2:00 ` [PATCH] sparc: fix compile failure ("struct resource" related) William Lee Irwin III
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=20050301134440.05ae1152.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adobriyan@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=wli@holomorphy.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