public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 REPOST 2/3] image: Implement IH_TYPE_KERNEL_REL
Date: Thu, 20 Oct 2011 23:46:35 +0200	[thread overview]
Message-ID: <20111020214635.F0901158D103@gemini.denx.de> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF173D51C286@HQMAIL01.nvidia.com>

Dear Stephen Warren,

In message <74CDBE0F657A3D45AFBB94109FB122FF173D51C286@HQMAIL01.nvidia.com> you wrote:
>
> > DOn;t give up to oearly.  My opinion is that #ifdef's are bad, and
> > increased code size is bad either.  If we can trade off one for the
> > other, we should know exactly what we can win here and how much we
> > have to pay for that there.  That's all I want to know.
> 
> Do you mean the total without /any/ ifdefs? If so, please see where I
> answered this question earlier in the thread:
> 
> http://lists.denx.de/pipermail/u-boot/2011-October/104427.html
> 
> The first time I submitted this patch, there were no ifdefs, and you
> stated that the additional 576 bytes text plus 136 bytes rodata was
> unacceptable, so I rewrote the patch to add ifdefs everywhere.

The statement that triggered me was "Maybe relax that by a few 10s of
bytes?", and my question was then ``how much is "a few 10s of bytes"''?

Obviously this must be something inbetween the 700+ bytes you state
here, and the zero bytes you state elsewhere.

I wonder what exactly it was, then?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Lots of folks confuse bad management with destiny.   -- Frank Hubbard

  reply	other threads:[~2011-10-20 21:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 21:11 [U-Boot] [PATCH v2 REPOST 1/3] [COSMETIC] checkpatch whitespace cleanups Stephen Warren
2011-10-18 21:11 ` [U-Boot] [PATCH v2 REPOST 2/3] image: Implement IH_TYPE_KERNEL_REL Stephen Warren
2011-10-19  0:56   ` Simon Glass
2011-10-19 15:55     ` Stephen Warren
2011-10-19 20:00       ` Wolfgang Denk
2011-10-19 21:58         ` Stephen Warren
2011-10-20 14:04           ` Wolfgang Denk
2011-10-20 15:43             ` Stephen Warren
2011-10-20 18:56               ` Wolfgang Denk
2011-10-20 19:03                 ` Stephen Warren
2011-10-20 19:09                   ` Simon Glass
2011-10-20 19:39                     ` Wolfgang Denk
2011-10-20 19:52                       ` Stephen Warren
2011-10-20 21:46                         ` Wolfgang Denk [this message]
2011-10-20 21:54                           ` Stephen Warren
2011-10-20 19:37                   ` Wolfgang Denk
2011-10-20 22:29   ` Simon Glass
2011-10-18 21:11 ` [U-Boot] [PATCH v2 REPOST 3/3] tegra2: Enable CONFIG_SYS_RELATIVE_IMAGES Stephen Warren
2011-10-19  1:03   ` Simon Glass
2011-10-19 15:24     ` Stephen Warren
2011-10-20 20:27       ` Simon Glass
2011-10-20 20:47         ` Stephen Warren
2011-10-20 22:27           ` Simon Glass
2011-10-19  0:01 ` [U-Boot] [PATCH v2 REPOST 1/3] [COSMETIC] checkpatch whitespace cleanups Simon Glass
2011-10-19  1:01 ` Simon Glass
2011-10-21 23:13 ` 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=20111020214635.F0901158D103@gemini.denx.de \
    --to=wd@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox