From: Geert Uytterhoeven <geert@linux-m68k•org>
To: Rob Landley <rob@landley•net>, Sam Ravnborg <sam@ravnborg•org>,
Greg Ungerer <gerg@snapgear•com>
Cc: linux-kernel@vger•kernel.org, dwmw2@infradead•org,
linux-next@vger•kernel.org
Subject: Re: make headers_install broken for ARCH=m68k in 2.6.29-rc7.
Date: Thu, 12 Mar 2009 23:40:02 +0100 [thread overview]
Message-ID: <10f740e80903121540i30fdaddr600ce21f4159530a@mail.gmail.com> (raw)
In-Reply-To: <20090312210216.GB14205@uranus.ravnborg.org>
On Thu, Mar 12, 2009 at 22:02, Sam Ravnborg <sam@ravnborg•org> wrote:
>>
>> And, yes, I can confirm the m68k include/asm/unistd.h from linux-next actually
>> has contents, thanks to commit 646652bded41f4c3bd375b4e03a25b42da93f40b
>>
>> Anyway, here's hoping the fix makes it into 2.6.29.
>
> Why not telling the m68k maintainer that you think it should go into 2.6.29?
>
> As it stand now we will ikely see another mail from you "I already said so"
> when we ship it broken but you did not care to tell relevant people.
>
> grep -C 5 -i m68k MAINTAINES revelas this:
> M68K ARCHITECTURE
> P: Geert Uytterhoeven
> M: geert@linux-m68k•org
> P: Roman Zippel
> M: zippel@linux-m68k•org
> L: linux-m68k@lists•linux-m68k.org
> W: http://www.linux-m68k.org/
> W: http://linux-m68k-cvs.ubb.ca/
> S: Maintained
>
>
> Sam
>
There are a few more:
param.h:#include "param_no.h"
param.h:#include "param_mm.h"
ptrace.h:#include "ptrace_no.h"
ptrace.h:#include "ptrace_mm.h"
setup.h:#include "setup_no.h"
setup.h:#include "setup_mm.h"
sigcontext.h:#include "sigcontext_no.h"
sigcontext.h:#include "sigcontext_mm.h"
siginfo.h:#include "siginfo_no.h"
siginfo.h:#include "siginfo_mm.h"
signal.h:#include "signal_no.h"
signal.h:#include "signal_mm.h"
swab.h:#include "swab_no.h"
swab.h:#include "swab_mm.h"
Rob, do these also causes problems?
Some (not all) of them are fixed in linux-next.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k•org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2009-03-12 22:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200903120437.03837.rob@landley.net>
[not found] ` <20090312095854.GA9398@uranus.ravnborg.org>
2009-03-12 20:03 ` make headers_install broken for ARCH=m68k in 2.6.29-rc7 Rob Landley
2009-03-12 20:58 ` Sam Ravnborg
2009-03-12 23:24 ` Stephen Rothwell
2009-03-12 21:02 ` Sam Ravnborg
2009-03-12 22:40 ` Geert Uytterhoeven [this message]
2009-03-13 3:25 ` Rob Landley
2009-03-13 7:04 ` Greg Ungerer
2009-03-13 8:25 ` Sam Ravnborg
2009-03-13 8:33 ` Geert Uytterhoeven
2009-03-13 8:59 ` Sam Ravnborg
2009-03-13 10:52 ` Greg Ungerer
2009-03-13 12:14 ` Geert Uytterhoeven
2009-03-16 12:40 ` Greg Ungerer
2009-03-16 20:20 ` Rob Landley
2009-03-16 22:08 ` Geert Uytterhoeven
2009-03-16 23:09 ` Greg Ungerer
2009-03-16 23:10 ` Greg Ungerer
2009-03-18 4:03 ` Rob Landley
2009-03-18 5:34 ` Greg Ungerer
2009-03-18 18:12 ` Rob Landley
2009-03-18 23:53 ` Greg Ungerer
2009-03-19 7:59 ` Geert Uytterhoeven
2009-03-19 8:41 ` Rob Landley
2009-03-13 8:25 ` Geert Uytterhoeven
2009-03-13 6:53 ` Greg Ungerer
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=10f740e80903121540i30fdaddr600ce21f4159530a@mail.gmail.com \
--to=geert@linux-m68k$(echo .)org \
--cc=dwmw2@infradead$(echo .)org \
--cc=gerg@snapgear$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rob@landley$(echo .)net \
--cc=sam@ravnborg$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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