From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Suniel Mahesh <sunil@amarulasolutions.com>,
Jagan Teki <jagan@amarulasolutions.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/5] Fix genimage build failure on Gitlab-CI
Date: Sun, 6 Feb 2022 10:32:16 +0100 [thread overview]
Message-ID: <20220206103216.6d89c19e@windsurf> (raw)
In-Reply-To: <20220203225957.3039320-1-giulio.benetti@benettiengineering.com>
On Thu, 3 Feb 2022 23:59:52 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Giulio Benetti (5):
> board/friendlyarm/nanopc-t4:use partition-type-uuid for genimage-15
> board/friendlyarm/nanopi-m4:use partition-type-uuid for genimage-15
> board/pine64/rockpro64:use partition-type-uuid for genimage-15
> board/radxa/rockpi-4:use partition-type-uuid for genimage-15
> board/radxa/rockpi-n10:use partition-type-uuid for genimage-15
Series applied, thanks
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-02-06 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 22:59 [Buildroot] [PATCH 0/5] Fix genimage build failure on Gitlab-CI Giulio Benetti
2022-02-03 22:59 ` [Buildroot] [PATCH 1/5] board/friendlyarm/nanopc-t4:use partition-type-uuid for genimage-15 Giulio Benetti
2022-02-03 22:59 ` [Buildroot] [PATCH 2/5] board/friendlyarm/nanopi-m4:use " Giulio Benetti
2022-02-03 22:59 ` [Buildroot] [PATCH 3/5] board/pine64/rockpro64:use " Giulio Benetti
2022-02-03 22:59 ` [Buildroot] [PATCH 4/5] board/radxa/rockpi-4:use " Giulio Benetti
2022-02-03 22:59 ` [Buildroot] [PATCH 5/5] board/radxa/rockpi-n10:use " Giulio Benetti
2022-02-06 9:32 ` Thomas Petazzoni via buildroot [this message]
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=20220206103216.6d89c19e@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=jagan@amarulasolutions.com \
--cc=sunil@amarulasolutions.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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