All of lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: Edgar Bonet <bonet@grenoble.cnrs.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 7/7] board/kontron/smarc-sal28/genimage.cfg: fix option suffix
Date: Tue, 9 Nov 2021 09:49:03 +0100	[thread overview]
Message-ID: <0815dcf4-bab0-bcb3-2084-44c876499f88@benettiengineering.com> (raw)
In-Reply-To: <03f9ad1a-21d0-a5ef-d563-86e1446d8545@grenoble.cnrs.fr>

Hi Edgar,

On 11/9/21 9:26 AM, Edgar Bonet wrote:
> Hello!
> 
> Michael Walle wrote:
>> There is no "K" prefix in si units. Stictly speaking there is no "KB";
>> there is a "kB" or a "KiB".
> 
> Although not a de jure standard, quite a few Linux tools have adopted
> the following convention:
> 
>      1 KB = 1000 B (i.e. 1 kB)
>      1 K  = 1024 B (i.e. 1 KiB)

+1

> Here is an excerpt from man losetup:
> 
>      The  size  and  offset  arguments may be followed by the
>      multiplicative suffixes KiB (=1024), MiB (=1024*1024), and so on
>      for  GiB,  TiB,  PiB, EiB,  ZiB and YiB (the "iB" is optional,
>      e.g., "K" has the same meaning as "KiB") or the suffixes KB
>      (=1000), MB (=1000*1000), and  so  on  for GB, TB, PB, EB, ZB
>      and YB.

This is a good description

> Given that this is a common Linux convention, "offset = 4K" makes it
> clearer that these are KiB ("offset = 4KiB" would be still clearer if
> supported).

Thank you
Best regards
-- 
Giulio Benetti
Benetti Engineering sas

> Regards,
> 
> Edgar.
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
> 

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-11-09  8:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08 23:05 [Buildroot] [PATCH 0/7] Post genimage.cfg beautify Giulio Benetti
2021-11-08 23:05 ` [Buildroot] [PATCH 1/7] board/olimex/a20_olinuxino/genimage.cfg: fix build failure due to wrong offset value suffix Giulio Benetti
2021-11-09  9:01   ` Luca Ceresoli
2021-11-09  9:16     ` Giulio Benetti
2021-11-08 23:05 ` [Buildroot] [PATCH 2/7] board/altera/socrates_cyclone5/genimage.cfg: fix offset suffix Giulio Benetti
2021-11-08 23:05 ` [Buildroot] [PATCH 3/7] board/friendlyarm/nanopi-neo2/genimage.cfg: fix comment Giulio Benetti
2021-11-08 23:05 ` [Buildroot] [PATCH 4/7] board/orangepi/orangepi-pc2/genimage.cfg: " Giulio Benetti
2021-11-08 23:05 ` [Buildroot] [PATCH 5/7] board/minnowboard/genimage.cfg: fix option assignment spaces Giulio Benetti
2021-11-08 23:05 ` [Buildroot] [PATCH 6/7] board/kontron/pitx-imx8m/genimage.cfg: fix option suffix Giulio Benetti
2021-11-09  7:37   ` Heiko Thiery
2021-11-09  7:49     ` Giulio Benetti
2021-11-08 23:05 ` [Buildroot] [PATCH 7/7] board/kontron/smarc-sal28/genimage.cfg: " Giulio Benetti
2021-11-09  8:04   ` Michael Walle
2021-11-09  8:26     ` Edgar Bonet
2021-11-09  8:49       ` Giulio Benetti [this message]
2021-11-09  8:38     ` Giulio Benetti
2021-11-09  8:50       ` Michael Walle
2021-11-09  8:50     ` Yann E. MORIN
2021-11-09  9:23       ` Arnout Vandecappelle

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=0815dcf4-bab0-bcb3-2084-44c876499f88@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.com \
    --cc=bonet@grenoble.cnrs.fr \
    --cc=buildroot@buildroot.org \
    /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.