From: Peter Korsgaard <peter@korsgaard.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org, samuel@sholland.org
Subject: Re: [Buildroot] [PATCH 2/2] configs/nezha_defconfig: new defconfig
Date: Fri, 05 Nov 2021 15:30:23 +0100 [thread overview]
Message-ID: <87czneisjk.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <AE14FCC4-756C-4549-A05A-9969D06243F5@benettiengineering.com> (Giulio Benetti's message of "Fri, 5 Nov 2021 14:52:47 +0100")
>>>>> "Giulio" == Giulio Benetti <giulio.benetti@benettiengineering.com> writes:
Hi,
>>> I find it to be easier to read.
>>
>> Ok. The "documentation" actually lists this in 512b sectors, but I don't
>> think genimage has something nice to handle this:
> I don’t think it should matter the block size because we’re describing
> in bytes, not in block size, if we say 8K it’s 8KB, 128KB is 128KB and
> so on. Correct?
Sure, just about readability - E.G. I don't know if 128K is a lot more
readable than 131072 if you are looking at documentation that says
sector 256, but OK.
> I let you know if this is needed for all .cfg files and if it works
> otherwise on those specific cases we can specify per byte. I find it
> more clear.
> Is ok?
For me it is, yes.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-11-05 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 12:38 [Buildroot] [PATCH 1/2] boot/sun20i-d1-spl: new package Peter Korsgaard
2021-11-05 12:38 ` [Buildroot] [PATCH 2/2] configs/nezha_defconfig: new defconfig Peter Korsgaard
2021-11-05 13:10 ` Thomas Petazzoni
2021-11-05 13:26 ` Peter Korsgaard
2021-11-05 13:28 ` Giulio Benetti
2021-11-05 13:35 ` Peter Korsgaard
2021-11-05 13:52 ` Giulio Benetti
2021-11-05 14:30 ` Peter Korsgaard [this message]
2021-11-07 0:49 ` Giulio Benetti
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=87czneisjk.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=samuel@sholland.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox