All of lore.kernel.org
 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 21:37:07 +0200	[thread overview]
Message-ID: <20111020193707.C2CDB158D103@gemini.denx.de> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF173D51C255@HQMAIL01.nvidia.com>

Dear Stephen Warren,

In message <74CDBE0F657A3D45AFBB94109FB122FF173D51C255@HQMAIL01.nvidia.com> you wrote:
>
> Sorry, but why exactly?

Because I'm short of time, and would consider it helpful if you
explain that you mean?

> The patch I posted doesn't add size to the U-Boot binary without the
> configuration option turned on, and I believe should be reviewable and
> hopefully even in a state ready to be replied without any further change
> or explanation.
> 
> Simon Glass questioned whether the change should be allowed to increase
> binary size even when disabled, so as to avoid adding at least some of
> the ifdefs. At present, I'm not going to pursue that since it's obvious
> that's not what you want.

You misunderstand.  I am interested in avoiding #ifdef's, but I'm also
interested in understanding exactly which price we have to pay
instead.

> Please, again, just take a look at the patch itself and ignore this part
> of the thread. I *really* don't think the patch needs any explanation in
> its current form.
> 
> At this point, I'm honestly tempted to just give up on these U-Boot patches.

Me too.


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
Never put off until tomorrow what you can put off indefinitely.

  parent reply	other threads:[~2011-10-20 19:37 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
2011-10-20 21:54                           ` Stephen Warren
2011-10-20 19:37                   ` Wolfgang Denk [this message]
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=20111020193707.C2CDB158D103@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 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.