From: Andrew Morton <akpm@osdl.org>
To: "Haavard Skinnemoen" <hskinnemoen@gmail.com>
Cc: "David Woodhouse" <dwmw2@infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
" Håvard Skinnemoen" <hskinnemoen@atmel.com>
Subject: Re: [PATCH] avr32 architecture
Date: Tue, 26 Sep 2006 16:40:42 -0700 [thread overview]
Message-ID: <20060926164042.203e3089.akpm@osdl.org> (raw)
In-Reply-To: <1defaf580609261417v4d3ea0f3pb10699d60ad0323f@mail.gmail.com>
On Tue, 26 Sep 2006 23:17:29 +0200
"Haavard Skinnemoen" <hskinnemoen@gmail.com> wrote:
> On 9/26/06, David Woodhouse <dwmw2@infradead.org> wrote:
> > On Tue, 2006-09-26 at 16:01 +0000, Linux Kernel Mailing List wrote:
> > > [PATCH] avr32 architecture
> >
> > pmac /pmac/git/linux-2.6 $ make ARCH=avr32 headers_check
> > CHK include/linux/version.h
> > make[1]: `scripts/unifdef' is up to date.
> > CHECK include/asm/user.h
> > CHECK include/asm/unistd.h
> > /pmac/git/linux-2.6/usr/include/asm/unistd.h requires linux/linkage.h, which does not exist in exported headers
>
> Right. avr32-implement-kernel_execve.patch, which was flagged as "Will
> merge" by Andrew, fixes it by moving the #ifdef __KERNEL__ guard to
> cover everything but the __NR_foo definitions.
Ho hum, such leakage happens sometimes.
> So as long as that
> one's still scheduled for inclusion, I think sending a separate patch
> to fix this problem will do more harm than good.
>
Yes, I'm planning on merging the execve cleanups for 2.6.19. It's probably
a week away yet.
prev parent reply other threads:[~2006-09-26 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200609261601.k8QG1Txd005700@hera.kernel.org>
2006-09-26 21:02 ` David Woodhouse
2006-09-26 21:17 ` Haavard Skinnemoen
2006-09-26 23:40 ` Andrew Morton [this message]
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=20060926164042.203e3089.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--cc=hskinnemoen@atmel.com \
--cc=hskinnemoen@gmail.com \
--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®