From: Joshua Watt <jpewhacker@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Ross Burton <Ross.Burton@arm.com>,
"meta-virtualization@lists.yoctoproject.org"
<meta-virtualization@lists.yoctoproject.org>
Subject: Re: [meta-virtualization][PATCH v2] classes/image-oci: Map image architecture correctly
Date: Tue, 7 Nov 2023 08:33:54 -0700 [thread overview]
Message-ID: <CAJdd5GZRHSZ6hKAon47eHCK9-+YFNxKn_RqQF-CwmBy3zz+5fA@mail.gmail.com> (raw)
In-Reply-To: <CADkTA4N5ZDEqt1FnpEE4A+JGBvG4NMqyPNMU6V6=qn66GNT7AA@mail.gmail.com>
On Tue, Nov 7, 2023 at 8:31 AM Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
>
> On Tue, Nov 7, 2023 at 9:51 AM Ross Burton <Ross.Burton@arm.com> wrote:
> >
> > On 7 Nov 2023, at 13:00, Bruce Ashfield <bruce.ashfield@gmail.com> wrote:
> > >
> > > I'll do both: branch and revert there.
> >
> > Sounds sensible, thanks.
> >
>
> As it turned out, reverting would of course leave the issue unfixed
> that Joshua was addressing.
>
> So I copied the mapping routine into the class and did a nanbield
> specific commit.
Thanks Bruce!
>
> Bruce
>
> > Ross
>
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
next prev parent reply other threads:[~2023-11-07 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 10:37 [meta-virtualization][PATCH v2] classes/image-oci: Map image architecture correctly Ross Burton
2023-11-07 13:00 ` Bruce Ashfield
2023-11-07 14:51 ` Ross Burton
2023-11-07 15:31 ` Bruce Ashfield
2023-11-07 15:33 ` Joshua Watt [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-16 21:26 [meta-virtualization][PATCH] classes/image-oci: Map x86_64 -> amd64 Joshua Watt
2023-10-30 19:08 ` [meta-virtualization][PATCH v2] classes/image-oci: Map image architecture correctly Joshua Watt
2023-11-03 3:25 ` Bruce Ashfield
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=CAJdd5GZRHSZ6hKAon47eHCK9-+YFNxKn_RqQF-CwmBy3zz+5fA@mail.gmail.com \
--to=jpewhacker@gmail.com \
--cc=Ross.Burton@arm.com \
--cc=bruce.ashfield@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).