From: Sam Ravnborg <sam@ravnborg.org>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org, dwmw2@infradead.org,
linux-next@vger.kernel.org, geert@linux-m68k.org
Subject: Re: make headers_install broken for ARCH=m68k in 2.6.29-rc7.
Date: Thu, 12 Mar 2009 22:02:16 +0100 [thread overview]
Message-ID: <20090312210216.GB14205@uranus.ravnborg.org> (raw)
In-Reply-To: <200903121503.37195.rob@landley.net>
>
> 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
next prev parent reply other threads:[~2009-03-12 21:00 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 9:37 make headers_install broken for ARCH=m68k in 2.6.29-rc7 Rob Landley
2009-03-12 9:58 ` Sam Ravnborg
2009-03-12 20:03 ` Rob Landley
2009-03-12 20:58 ` Sam Ravnborg
2009-03-12 23:24 ` Stephen Rothwell
2009-03-12 21:02 ` Sam Ravnborg [this message]
2009-03-12 22:40 ` Geert Uytterhoeven
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-13 12:14 ` Geert Uytterhoeven
2009-03-16 12:40 ` Greg Ungerer
2009-03-16 12:40 ` Greg Ungerer
2009-03-16 20:20 ` Rob Landley
2009-03-16 20:20 ` Rob Landley
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-16 23:10 ` Greg Ungerer
2009-03-18 4:03 ` Rob Landley
2009-03-18 4:03 ` Rob Landley
2009-03-18 5:34 ` Greg Ungerer
2009-03-18 5:34 ` Greg Ungerer
2009-03-18 5:34 ` Greg Ungerer
2009-03-18 18:12 ` Rob Landley
2009-03-18 18:12 ` Rob Landley
2009-03-18 18:12 ` Rob Landley
2009-03-18 23:53 ` Greg Ungerer
2009-03-18 23:53 ` Greg Ungerer
2009-03-18 23:53 ` Greg Ungerer
2009-03-19 7:59 ` Geert Uytterhoeven
2009-03-19 7:59 ` Geert Uytterhoeven
2009-03-19 8:41 ` Rob Landley
2009-03-16 12:40 ` Greg Ungerer
2009-03-13 8:25 ` Geert Uytterhoeven
2009-03-13 6:53 ` Greg Ungerer
2009-04-01 16:57 ` Lennart Sorensen
2009-04-01 19:03 ` Sam Ravnborg
2009-04-01 19:48 ` Lennart Sorensen
2009-04-01 20:23 ` Geert Uytterhoeven
2009-04-01 22:59 ` Lennart Sorensen
2009-04-02 2:14 ` Rob Landley
2009-04-02 21:59 ` Lennart Sorensen
2009-04-03 0:24 ` Rob Landley
2009-04-03 4:10 ` Lennart Sorensen
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=20090312210216.GB14205@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=dwmw2@infradead.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rob@landley.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.