From: Alexander Kanavin <alex.kanavin@gmail.com>
To: "Enrico Jörns" <ejo@pengutronix.de>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Marco Felsch <m.felsch@pengutronix.de>,
openembedded-core@lists.openembedded.org, yocto@pengutronix.de,
barebox@lists.infradead.org
Subject: Re: [yocto] [OE-core] [PATCH 1/2] barebox: add initial support
Date: Wed, 15 Feb 2023 16:12:36 +0100 [thread overview]
Message-ID: <CANNYZj8UMuzxfXjXx4-pn+a1RXxmccqsq2uiXceqE8VM2NdTBg@mail.gmail.com> (raw)
In-Reply-To: <721e4d45d0d67a03be6ea4953351f5cb0c4ac36d.camel@pengutronix.de>
There was a parallel conversation on the irc meanwhile; we've
concluded that Enrico will look into adding qemu based tests for
barebox into oe-selftest like we already have for EFI bootloaders, and
there will be a new patchset then.
Alex
On Wed, 15 Feb 2023 at 16:01, Enrico Jörns <ejo@pengutronix.de> wrote:
>
> Am Mittwoch, dem 15.02.2023 um 15:11 +0100 schrieb Alexander Kanavin:
> > On Wed, 15 Feb 2023 at 14:53, Otavio Salvador
> > <otavio.salvador@ossystems.com.br> wrote:
> > > I think the Barebox inside OE-Core allows a bigger integration and
> > > reuse of existing tooling for signing and other classes currently well
> > > integrated with U-Boot. For me, a critical point for decision is if
> > > Pengutronix will commit to support it.
> >
> > You should be well aware there's a history of people contributing
> > stuff to core and even assigning themselves as maintainers, then
> > disappearing.
>
> If possible I would add my name with the above-mentioned Mailing list to the maintainers file.
> This ensures I am responsible but not the only one reading the mails.
>
> > And then it falls (largely) on me to keep things
> > (barely) going. What happens if ptx withdraws its commitment? Can I
> > then send a commit that removes barebox from core? Imagine the angry
> > lynch mob that will show up after my head.
>
> I am fully ok with removing barebox again if we fail maintaining it properly.
>
> Should I sign this somewhere? ;)
>
> > Adding things to core is a decision that cannot be easily reversed, so
> > I'd rather have barebox in meta-barebox for a while, with any needed
> > fixing to classes and infra in core.
>
> It has been in meta-ptx since 2015 and in meta-barebox since 2016. I would call that 'a while' :)
>
>
> Best regards, Enrico
>
> --
> Pengutronix e.K. | Enrico Jörns |
> Embedded Linux Consulting & Support | https://www.pengutronix.de/ |
> Steuerwalder Str. 21 | Phone: +49-5121-206917-180 |
> 31137 Hildesheim, Germany | Fax: +49-5121-206917-9 |
>
prev parent reply other threads:[~2023-02-15 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230203135011.2061939-1-m.felsch@pengutronix.de>
[not found] ` <12e370a3183d04572da1c5749d8e64dcf5091a0c.camel@linuxfoundation.org>
2023-02-14 9:46 ` Enrico Jörns
2023-02-14 13:56 ` Richard Purdie
[not found] ` <CAP9ODKokQpGL3ttukqRaq3-8m0ci7qp8mckbgudGJx1HOu-fPw@mail.gmail.com>
2023-02-15 13:43 ` Alexander Kanavin
2023-02-15 13:49 ` Enrico Jörns
2023-02-15 13:53 ` Otavio Salvador
2023-02-15 14:06 ` Enrico Jörns
2023-02-15 14:11 ` Alexander Kanavin
2023-02-15 14:59 ` Otavio Salvador
2023-02-15 15:01 ` Enrico Jörns
2023-02-15 15:12 ` Alexander Kanavin [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=CANNYZj8UMuzxfXjXx4-pn+a1RXxmccqsq2uiXceqE8VM2NdTBg@mail.gmail.com \
--to=alex.kanavin@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=ejo@pengutronix.de \
--cc=m.felsch@pengutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto@pengutronix.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