From: Robert Schwebel <r.schwebel@pengutronix.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [RFD] Consistent debugging output structure
Date: Mon, 24 Mar 2003 09:59:22 +0100 [thread overview]
Message-ID: <20030324085922.GD28544@pengutronix.de> (raw)
In-Reply-To: <20030324085228.B50C4C58BA@atlas.denx.de>
On Mon, Mar 24, 2003 at 09:52:23AM +0100, Wolfgang Denk wrote:
> I have answered this question before. I see no need for such a patch
> in the common code. You can easily implement it using the existing
> debug() macro if you feel you need it in your own code.
>
> I will reject such a patch if it globally effects all boards and all
> common code.
How could it affect other implementations if, additionally to the
existing debug() function, debug2() and debug3() are added? Sorry, but I
don't understand your arguments. I've never said that I wanted to change
the whole code at once.
Robert
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Braunschweiger Str. 79, 31134 Hildesheim, Germany
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4
next prev parent reply other threads:[~2003-03-24 8:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 18:32 [U-Boot-Users] [RFD] Consistent debugging output structure Robert Schwebel
2003-03-22 10:28 ` Robert Schwebel
2003-03-22 21:35 ` Vladimir Gurevich
2003-03-23 0:51 ` Vladimir Gurevich
2003-03-23 14:32 ` Wolfgang Denk
2003-03-24 6:29 ` Robert Schwebel
2003-03-24 8:14 ` Wolfgang Denk
2003-03-24 8:23 ` Robert Schwebel
2003-03-24 8:52 ` Wolfgang Denk
2003-03-24 8:59 ` Robert Schwebel [this message]
2003-03-24 9:10 ` Wolfgang Denk
2003-03-24 7:44 ` Holger Schurig
2003-03-24 8:36 ` Robert Schwebel
2003-03-24 8:57 ` Wolfgang Denk
2003-03-24 9:03 ` Robert Schwebel
2003-03-24 9:19 ` Wolfgang Denk
2003-03-24 8:50 ` Wolfgang Denk
2003-03-24 9:00 ` Robert Schwebel
2003-03-24 9:16 ` Wolfgang Denk
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=20030324085922.GD28544@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--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 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.