From: Jon Loeliger <jdl@jdl•com>
To: Paul Gortmaker <paul.gortmaker@windriver•com>
Cc: linuxppc-dev@ozlabs•org, devicetree-discuss@ozlabs•org
Subject: Re: [PATCH] dtc: give advance warning that "-S" is going away.
Date: Thu, 31 Jul 2008 10:43:41 -0500 [thread overview]
Message-ID: <E1KOaJZ-0006NA-Sl@jdl.com> (raw)
In-Reply-To: <1217426356-1248-1-git-send-email-paul.gortmaker@windriver.com>
> The "-S" option allowed the specification of a minimum size for
> the blob, however the main reason for caring about the size is
> so there is enough padding to add a chosen node by u-boot or
> whoever. In which case, folks don't really care about the absolute
> size, but rather the size of the padding added for this -- which
> is what the "-p" option does. Having the "-S" just confuses people.
>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver•com>
Applied.
jdl
prev parent reply other threads:[~2008-07-31 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1KOBwm-0002vc-CT@jdl.com>
2008-07-30 13:59 ` [PATCH] dtc: give advance warning that "-S" is going away Paul Gortmaker
2008-07-30 14:03 ` Jon Loeliger
2008-07-31 15:43 ` Jon Loeliger [this message]
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=E1KOaJZ-0006NA-Sl@jdl.com \
--to=jdl@jdl$(echo .)com \
--cc=devicetree-discuss@ozlabs$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paul.gortmaker@windriver$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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