Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Roberto Medina <robertoxmed@gmail.com>
To: Kilian Zinnecker <kilian.zinnecker@mail.de>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1 v3] configs/roc_rk3399_pc: Bring back and update the configuration for the rockchip rk3399 built by firefly.
Date: Fri, 11 Aug 2023 22:59:35 +0200	[thread overview]
Message-ID: <bf3eb1b7-2bee-4cbe-bc43-49660535c94c@gmail.com> (raw)
In-Reply-To: <10318288.nUPlyArG6x@kilian-aisec>

Hi Kilian,

Thanks for reviewing as usual.

On 8/11/23 21:02, Kilian Zinnecker wrote:
>> diff --git a/DEVELOPERS b/DEVELOPERS
>> index 6ffa3ee693..5ebabd01cb 100644
>> --- a/DEVELOPERS
>> +++ b/DEVELOPERS
>> @@ -2546,6 +2546,10 @@ F:	package/mhz/
>>   N:	Robert Rose <robertroyrose@gmail.com>
>>   F:	package/grpc/
>>
>> +N:	Roberto Medina <robertoxmed@gmail.com>
>> +F:	configs/roc_pc_rk3399_defconfig
>> +F:	board/firefly/roc-rk3399
> 
> I think when it comes to repositories (i.e., board/firefly/roc-rk3399) it is
> best practice to add a trailing space. I guess this way one can easily
> distinguish directories from single files.

Noted for the trailing slash.

>> +BR2_TARGET_UBOOT_CUSTOM_VERSION=y
>> +BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2022.04"
> 
> I think 2022.04 is actually the current default version of buildroot. So
> unless you have reason to freeze it to this version on purpose (e.g., because
> older and newer versions are known to be not working with this board - which I
> don't believe is the case) you could simply omit these two lines.

Actually in v2 of this patch, Thomas requested to set a fixed version 
for U-Boot (mail from 08/08). Which made sense to me as TFA and Linux 
have a fixed version as well.

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

  parent reply	other threads:[~2023-08-11 20:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 16:25 [Buildroot] [PATCH 0/1 v3] onfigs/roc_rk3399_pc: Bring back and update the configuration for the rockchip rk3399 built by firefly Roberto Medina
2023-08-11 16:25 ` [Buildroot] [PATCH 1/1 v3] configs/roc_rk3399_pc: " Roberto Medina
2023-08-11 19:02   ` Kilian Zinnecker via buildroot
2023-08-11 19:07     ` Kilian Zinnecker via buildroot
2023-08-11 20:59     ` Roberto Medina [this message]
2023-08-11 21:59       ` Kilian Zinnecker via buildroot
2023-08-12 20:00         ` Thomas Petazzoni via buildroot
2023-08-12 19:58   ` Thomas Petazzoni via buildroot
2023-08-12 20:22     ` Roberto Medina

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=bf3eb1b7-2bee-4cbe-bc43-49660535c94c@gmail.com \
    --to=robertoxmed@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=kilian.zinnecker@mail.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