From: James Simmons <jsimmons@infradead.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Adrian Bunk <bunk@fs.tum.de>, "Randy.Dunlap" <rddunlap@osdl.org>,
"Justin T. Gibbs" <gibbs@scsiguy.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: 2.6: spurious recompiles
Date: Tue, 9 Sep 2003 00:45:00 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0309090044400.23354-100000@phoenix.infradead.org> (raw)
In-Reply-To: <20030907053309.GA963@mars.ravnborg.org>
> > 2. pnmtologo
> > The following happens again once, but not when doing a third "make":
> > ./scripts/pnmtologo -t mono -n logo_linux_mono -o drivers/video/logo/logo_linux_mono.c drivers/video/logo/logo_linux_mono.pbm
> > CC drivers/video/logo/logo_linux_mono.o
> > ./scripts/pnmtologo -t vga16 -n logo_linux_vga16 -o drivers/video/logo/logo_linux_vga16.c drivers/video/logo/logo_linux_vga16.ppm
> > CC drivers/video/logo/logo_linux_vga16.o
> > ./scripts/pnmtologo -t clut224 -n logo_linux_clut224 -o drivers/video/logo/logo_linux_clut224.c drivers/video/logo/logo_linux_clut224.ppm
> > CC drivers/video/logo/logo_linux_clut224.o
> > LD drivers/video/logo/built-in.o
> > LD drivers/video/built-in.o
>
> I have sent a patch to James Simmons some time ago. I will try to dig it
> up and see if it still applies, and fixes the problem.
I have the patch in the fbdev BK tree.
next prev parent reply other threads:[~2003-09-08 23:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 20:14 2.6: spurious recompiles Adrian Bunk
2003-09-06 22:33 ` Randy.Dunlap
2003-09-07 10:37 ` Adrian Bunk
2003-09-07 5:33 ` Sam Ravnborg
2003-09-08 23:45 ` James Simmons [this message]
2003-09-07 5:51 ` Sam Ravnborg
2003-09-07 7:00 ` Sam Ravnborg
2003-09-07 10:17 ` Adrian Bunk
2003-09-08 23:45 ` James Simmons
[not found] <20030906201417.GI14436@fs.tum.de.suse.lists.linux.kernel>
[not found] ` <33384.4.4.25.4.1062887601.squirrel@www.osdl.org.suse.lists.linux.kernel>
2003-09-06 22:44 ` Andi Kleen
2003-09-07 5:36 ` 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=Pine.LNX.4.44.0309090044400.23354-100000@phoenix.infradead.org \
--to=jsimmons@infradead.org \
--cc=bunk@fs.tum.de \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).