From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jamin Lin <jamin_lin@aspeedtech.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 0/2] kernel-fitimage/uboot-sign: support 64bits address
Date: Thu, 04 May 2023 12:45:14 +0100 [thread overview]
Message-ID: <7fe7561794aa4df74db87f013fc376ece2299888.camel@linuxfoundation.org> (raw)
In-Reply-To: <20230413103109.5604-1-jamin_lin@aspeedtech.com>
On Thu, 2023-04-13 at 18:31 +0800, Jamin Lin wrote:
> v1:
> kernel-fitimage.bbclass: allow users to change address-cells
> to support 64bits address
> uboot-sign.bbclass: allow users to change address-cells
> to support 64bits address.
>
> Jamin Lin (2):
> kernel-fitimage: support 64 bits address
> uboot-sign: support 64bits address
>
> meta/classes-recipe/kernel-fitimage.bbclass | 6 +++++-
> meta/classes-recipe/uboot-sign.bbclass | 6 +++++-
> 2 files changed, 10 insertions(+), 2 deletions(-)
Since this adds new variables, could you send patches to the
documentation please to document them?
I did also wonder if there was some way we could combine and share some
of this fit image information since we appear to have two variables
with different names encoding the same info here :/. Maybe that is
something we could fix or improve in a later patch?
I'm kind of living in hope we can simplify some of these different
places to share code ultimately.
Cheers,
Richard
prev parent reply other threads:[~2023-05-04 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 10:31 [PATCH 0/2] kernel-fitimage/uboot-sign: support 64bits address Jamin Lin
2023-04-13 10:31 ` [PATCH 1/2] kernel-fitimage: support 64 bits address Jamin Lin
2023-04-13 16:04 ` [OE-core] " Luca Ceresoli
2023-04-14 2:06 ` Jamin Lin
2023-04-13 10:31 ` [PATCH 2/2] uboot-sign: support 64bits address Jamin Lin
2023-05-04 11:45 ` Richard Purdie [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=7fe7561794aa4df74db87f013fc376ece2299888.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jamin_lin@aspeedtech.com \
--cc=openembedded-core@lists.openembedded.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