From: Haavard Skinnemoen <hskinnemoen@atmel.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] AVR32 update for 2.6.18-rc2-mm1
Date: Mon, 31 Jul 2006 15:55:15 +0200 [thread overview]
Message-ID: <1154354115351-git-send-email-hskinnemoen@atmel.com> (raw)
Hi Andrew,
I'm back from vacation, so I figured I should try to compile the latest
-mm for AVR32. It failed immediately, so here's a set of patches to fix
the breakage. I guess I should have tried a clean build before
submitting the last update, as I would have noticed that
include/config/MARKER doesn't exist anymore.
Anyway, 2.6.18-rc2-mm1 boots successfully on my target with these
patches, but there's something strange going on with NFS and a few
other things that I didn't notice on 2.6.18-rc1. I'll investigate
some more and see if I can figure out what's going on.
Do you want me to keep sending incremental patches, by the way? I can
fold everything (or at least the trivial stuff) into avr32-arch.patch
if you want.
Here's a shortlog of the patches coming up:
AVR32: Use auto.conf instead of MARKER
AVR32: Don't assume anything about MAX_NR_ZONES
AVR32: Add nsproxy definition
AVR32: Add I/O port access primitives
AVR32: Use linux/pfn.h
AVR32: Kill CONFIG_DISCONTIGMEM support completely
Haavard
next reply other threads:[~2006-07-31 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 13:55 Haavard Skinnemoen [this message]
2006-07-31 15:46 ` Haavard Skinnemoen
2006-07-31 18:40 ` Trond Myklebust
2006-08-01 8:12 ` Haavard Skinnemoen
2006-08-01 16:47 ` Trond Myklebust
2006-08-02 7:45 ` Haavard Skinnemoen
2006-08-03 14:34 ` Trond Myklebust
2006-08-03 15:33 ` Haavard Skinnemoen
2006-08-03 15:46 ` David Howells
2006-08-01 17:39 ` David Howells
2006-08-01 18:08 ` Trond Myklebust
2006-08-01 18:22 ` David Howells
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=1154354115351-git-send-email-hskinnemoen@atmel.com \
--to=hskinnemoen@atmel.com \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®