public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Leon Busch-George <leon@georgemail.eu>
To: u-boot@lists.denx.de
Cc: Dragan Simic <dsimic@manjaro.org>
Subject: Re: [PATCH] Makefile: use shell to calculate map_size
Date: Mon, 4 Mar 2024 16:57:50 +0100	[thread overview]
Message-ID: <20240304165750.162db44c@couch-potassium> (raw)
In-Reply-To: <20240304154007.67df1822@couch-potassium>

Oops!
That should have went to the list as well...

On Mon, 4 Mar 2024 15:40:07 +0100
Leon Busch-George <leon@georgemail.eu> wrote:

> Hi Dragan :-)
> 
> Thanks for your reply!
> 
> On Sat, 02 Mar 2024 22:13:08 +0100
> Dragan Simic <dsimic@manjaro.org> wrote:
> 
> > > +		awk '/_image_copy_start/ {start = $$1}
> > > /_image_binary_end/ {end = $$1} END {if (start != "" && end != "")
> > > print "echo $$((0x" toupper(end) " - 0x" toupper(start) "))"}' \
> > >  		| sed 's/0X//g' \
> > > -		| bc); \
> > > +		| sh); \
> > 
> > Maybe "sh -s" could be used instead, just for some additional
> > strictness.
> 
> -s is the default already but I see no reason against adding it.
> Allow me to offer another idea to improve strictness (I'll send a v2):
> 
>     awk '.. print end " " start ..' | sh -c 'read end start; echo
> $((end - start))'
> 
> That gets rid off sed and the interface between awk and sh is much
> cleaner (only the two numbers on one line rather than shell code).
> Sadly, the sed 's/0X//g' was introduced without an explanation in
> 3ce7a4fefa and but, looking at it more, I'm farly confident it was
> only for bc.
> 
> kind regards,
> Leon

  parent reply	other threads:[~2024-03-04 16:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02 13:17 [PATCH] Makefile: use shell to calculate map_size Leon M. Busch-George
2024-03-02 21:13 ` Dragan Simic
     [not found]   ` <20240304154007.67df1822@couch-potassium>
2024-03-04 15:57     ` Leon Busch-George [this message]
2024-03-04 20:38 ` [PATCH v2] " Leon M. Busch-George
2024-03-05 16:40   ` Leon Busch-George
2024-03-05 16:46   ` [PATCH v3] " Leon M. Busch-George
     [not found]     ` <343281d5cf78e8c473e40f58361e01e1@manjaro.org>
2024-03-10 10:33       ` Dragan Simic
     [not found]   ` <b594973ddce475d2a2baead6f4028134@manjaro.org>
2024-03-10 10:12     ` [PATCH v2] " Dragan Simic

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=20240304165750.162db44c@couch-potassium \
    --to=leon@georgemail.eu \
    --cc=dsimic@manjaro.org \
    --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