Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Brandon Maier" <brandon.maier@gmail.com>
To: "Akhilesh Nema" <nemaakhilesh@gmail.com>, <buildroot@buildroot.org>
Cc: "Brandon Maier" <brandon.maier@collins.com>
Subject: Re: [Buildroot] [PATCH 1/5] package/qoriq-rcw: bump version to lf-6.6.52-2.2.0
Date: Mon, 17 Feb 2025 20:11:05 -0600	[thread overview]
Message-ID: <D7V7GLF6R2JQ.3CH0YHV3C16UX@gmail.com> (raw)
In-Reply-To: <CAMV0Ro-AWc6Ugxsgks2zhVzvNkpVWW0zoJSvYfQ0STh2D4yu8A@mail.gmail.com>

Hi Akhnilesh,

On Wed Feb 12, 2025 at 11:42 AM CST, Akhilesh Nema wrote:
> On Fri, Jan 10, 2025 at 10:37 PM Akhilesh Nema <nemaakhilesh@gmail.com>
> wrote:
>
>> Changelog:
>> https://github.com/nxp-qoriq/rcw/compare/lf-6.6.23-2.0.0...lf-6.6.52-2.2.0
>>
>> Signed-off-by: Akhilesh Nema <nemaakhilesh@gmail.com>
>> ---
>>  package/qoriq-rcw/qoriq-rcw.hash | 2 +-
>>  package/qoriq-rcw/qoriq-rcw.mk   | 2 +-
>>  2 files changed, 2 insertions(+), 2 deletions(-)
>>
>
> Could you please review this patch series?

The series looks good to me, other then the ls1046a-frwy patch needs a
minor correction.

>
> The following defconfigs require the latest LF release tags to satisfy all
> dependencies:
>
> https://github.com/buildroot/buildroot/blob/master/configs/ls1046a-frwy_defconfig
> https://github.com/buildroot/buildroot/blob/master/configs/ls1046a-rdb_defconfig
> https://github.com/buildroot/buildroot/blob/master/configs/ls1043a-rdb_defconfig
>
> LF version tags are a new approach introduced by NXP. If this method is
> intended to be used consistently for future releases, it might be worth
> considering the introduction of a buildroot config option to store the LF
> version to simplify version upgrades for NXP boards.

It would be nice to make the update process easier. Though I find most
of the work is updating the hashes for each package. You can always
submit patches if you want to take a shot at it.

Thanks!
Brandon Maier

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

  reply	other threads:[~2025-02-18  2:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-11  6:37 [Buildroot] [PATCH 1/5] package/qoriq-rcw: bump version to lf-6.6.52-2.2.0 Akhilesh Nema
2025-01-11  6:37 ` [Buildroot] [PATCH 2/5] package/qoriq-fm-ucode: " Akhilesh Nema
2025-02-18  1:53   ` Brandon Maier
2025-01-11  6:37 ` [Buildroot] [PATCH 3/5] package/fmlib: " Akhilesh Nema
2025-02-18  1:54   ` Brandon Maier
2025-01-11  6:37 ` [Buildroot] [PATCH 4/5] package/fmc: " Akhilesh Nema
2025-02-18  1:55   ` Brandon Maier
2025-01-11  6:37 ` [Buildroot] [PATCH 5/5] configs/ls1046a-frwy_defconfig: bump BSP components " Akhilesh Nema
2025-02-18  1:57   ` Brandon Maier
2025-02-12 17:42 ` [Buildroot] [PATCH 1/5] package/qoriq-rcw: bump version " Akhilesh Nema
2025-02-18  2:11   ` Brandon Maier [this message]
2025-02-18  1:52 ` Brandon Maier
2025-03-15 15:43 ` Julien Olivain

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=D7V7GLF6R2JQ.3CH0YHV3C16UX@gmail.com \
    --to=brandon.maier@gmail.com \
    --cc=brandon.maier@collins.com \
    --cc=buildroot@buildroot.org \
    --cc=nemaakhilesh@gmail.com \
    /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