From: Rodolfo Giometti <giometti@enneenne.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] LOGO: All logos must be placed into the "logos" directory.
Date: Fri, 25 May 2007 16:52:46 +0200 [thread overview]
Message-ID: <20070525145246.GF21180@enneenne.com> (raw)
In-Reply-To: <20070525142604.C486C352B1F@atlas.denx.de>
On Fri, May 25, 2007 at 04:26:04PM +0200, Wolfgang Denk wrote:
> In message <20070525142001.GD4199@enneenne.com> you wrote:
> >
> > Subject: ... All logos must be placed into the "logos" directory.
>
> Why?
>
> > ifeq ($(LOGO_BMP),)
> > -LOGO_BMP= logos/denx.bmp
> > +LOGO_BMP= denx.bmp
>
> Which problem is this supposed to fix? I don't see any advantage, but
> I see the disadvantage that with your patch you cannot chose to place
> your logo - say - in board/.../ any more.
I don't want to fix any problem, I just wish to define some
standards... doing like this I force all logo files to be inside
tools/logos directory.
Currently logos are supposed to be under tools directory which is not
the proper place for them:
$(LOGO_H): $(obj)bmp_logo logos/$(LOGO_BMP)
$(obj)./bmp_logo logos/$(LOGO_BMP) >$@
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti at enneenne.com
Linux Device Driver giometti at gnudd.com
Embedded Systems giometti at linux.it
UNIX programming phone: +39 349 2432127
next prev parent reply other threads:[~2007-05-25 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 14:20 [U-Boot-Users] [PATCH] LOGO: All logos must be placed into the "logos" directory Rodolfo Giometti
2007-05-25 14:26 ` Wolfgang Denk
2007-05-25 14:52 ` Rodolfo Giometti [this message]
2007-05-25 15:43 ` Wolfgang Denk
2007-05-25 16:02 ` Rodolfo Giometti
2007-05-27 14:58 ` [U-Boot-Users] [PATCH] LOGO: Allow each board to define its own logo Rodolfo Giometti
2007-05-27 20:58 ` Wolfgang Denk
2007-05-28 7:52 ` Rodolfo Giometti
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=20070525145246.GF21180@enneenne.com \
--to=giometti@enneenne.com \
--cc=u-boot@lists.denx.de \
/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