From: Adrian Bunk <bunk@kernel.org>
To: Tim Schmielau <T.Schmielau@shu.ac.uk>
Cc: David Woodhouse <dwmw2@infradead.org>,
Sam Ravnborg <sam@ravnborg.org>,
Vegard Nossum <vegard.nossum@gmail.com>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jan Engelhardt <jengelh@computergmbh.de>,
geert@linux-m68k.org, zippel@linux-m68k.org
Subject: Re: [PATCH] Speed up "make headers_*"
Date: Thu, 26 Jun 2008 10:11:41 +0300 [thread overview]
Message-ID: <20080626071141.GN10285@cs181140183.pp.htv.fi> (raw)
In-Reply-To: <5DC8DBC2-AA22-448B-8646-06D5788C00FE@shu.ac.uk>
On Thu, Jun 26, 2008 at 02:59:21AM +0100, Tim Schmielau wrote:
> [apologies for the late reply, I do not follow lkml anymore]
>
> On Sun, 2008-06-08 at 14:17 +0100, David Woodhouse wrote:
>> On Sun, 2008-06-08 at 13:17 +0200, Sam Ravnborg wrote:
>> > #if !defined(CONFIG_M68K) || !defined(__KERNEL__)
>>
>> That's just scary, and broken for m68k where in userspace neither
>> CONFIG_M68K nor __KERNEL__ will be defined, so the unwanted ac_ahz
>> member will actually show up and break the binary compatibility.
>> Assuming we _don't_ want the ac_ahz member to be included on m68k,
>> this
>> should fix it (is __mc68000__ the right thing to use?)...
>>
>> diff --git a/include/linux/acct.h b/include/linux/acct.h
>> index e8cae54..228473b 100644
>> --- a/include/linux/acct.h
>> +++ b/include/linux/acct.h
>> @@ -58,8 +58,7 @@ struct acct
>> comp_t ac_minflt; /* Minor Pagefaults */
>> comp_t ac_majflt; /* Major Pagefaults */
>> comp_t ac_swaps; /* Number of Swaps */
>> -/* m68k had no padding here. */
>> -#if !defined(CONFIG_M68K) || !defined(__KERNEL__)
>> +#ifndef __mc68000__ /* m68k had no padding here. */
>> __u16 ac_ahz; /* AHZ */
>> #endif
>> __u32 ac_exitcode; /* Exitcode */
struct acct as provided by the kernel anyway differs from the one
shipped by glibc in /usr/include/sys/acct.h since your
"BSD accounting format rework" patch back in 2004.
Does the pre-v3 stuff actually work?
My first impression is that it doesn't and should therefore be removed.
> This would make cross-compiled m68k kernels silently write wrong
> accounting files.
>...
Cross-compiling can't make any difference here.
> Tim
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-06-26 7:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 1:59 Tim Schmielau
2008-06-26 7:11 ` Adrian Bunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-08 9:47 Sam Ravnborg
2008-06-08 10:12 ` Vegard Nossum
2008-06-08 10:41 ` Sam Ravnborg
2008-06-08 10:49 ` David Woodhouse
2008-06-08 11:17 ` Sam Ravnborg
2008-06-08 12:23 ` Oleg Verych
2008-06-08 13:17 ` David Woodhouse
2008-06-08 17:06 ` Segher Boessenkool
2008-06-08 17:34 ` Andreas Schwab
2008-06-08 19:45 ` Segher Boessenkool
2008-06-08 20:36 ` Geert Uytterhoeven
2008-06-08 11:01 ` WANG Cong
2008-06-08 11:18 ` Sam Ravnborg
2008-06-08 11:06 ` Vegard Nossum
2008-06-08 11:20 ` Sam Ravnborg
2008-06-08 11:20 ` David Woodhouse
2008-06-08 11:30 ` Sam Ravnborg
2008-06-08 11:47 ` David Woodhouse
2008-06-08 12:14 ` David Woodhouse
2008-06-08 12:29 ` David Woodhouse
2008-06-08 20:07 ` Sam Ravnborg
2008-06-08 20:58 ` David Woodhouse
2008-06-08 21:13 ` Sam Ravnborg
2008-06-09 6:23 ` Sam Ravnborg
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=20080626071141.GN10285@cs181140183.pp.htv.fi \
--to=bunk@kernel.org \
--cc=T.Schmielau@shu.ac.uk \
--cc=dwmw2@infradead.org \
--cc=geert@linux-m68k.org \
--cc=jengelh@computergmbh.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@gmail.com \
--cc=zippel@linux-m68k.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®