From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Markus Volk <f_l_k@t-online.de>,
openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCHv6] vte: upgrade 2.72.2 -> 2.74.0
Date: Fri, 22 Sep 2023 08:42:02 +0200 [thread overview]
Message-ID: <20230922064202279c2c00@mail.local> (raw)
In-Reply-To: <CANNYZj9JH-gcfAQad2y7SQuq2aMQ--=8J65xe--fW2gG3j4=TQ@mail.gmail.com>
On 22/09/2023 07:18:07+0200, Alexander Kanavin wrote:
> On Thu, 21 Sept 2023 at 22:59, Alexandre Belloni via
> lists.openembedded.org
> <alexandre.belloni=bootlin.com@lists.openembedded.org> wrote:
> >
> > BTW, I'd like you to test patches before sending because you claimed
> > this was tested with oe-core but this was definitively not. The fact
> > that we are at v6 and this still breaks builds so early is very
> > annoying.
>
> Was this claimed somewhere? I am not seeing it. The latest breakage is
> on an esoteric configuration (oecore without poky, which has a
> different set of default distro features), so I do not think it is
> fair to expect submissions would be tested there upfront.
>
IT was on v3. nodistro is not an esoteric configuration. Honestly,
while poky is great for testing, this is an awful distro for an actual
product. Way to many features are enabled for most of the embedded
platforms.
> Testing on poky for a basic target is expected, and was done, but
> things like 32 bit, musl, retro computing platforms like ppc or mips
> are on the AB to run through. Otherwise submitters will just decide
> it's not worth the trouble to contribute, and we're back to me doing
> the bulk of the updates, which is the outcome I am not going to
> appreciate.
I agree and I don't expect anyone to test mips, ppc, musl or x32 on
their own but having a patch building fine with nodistro is a basic
test.
32bit is pretty much alive though as we have seen new 32bit SoCs getting
released this year. There were even ARMv5 SoCs released just last year.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-09-22 6:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 18:15 [oe-core][PATCHv6] vte: upgrade 2.72.2 -> 2.74.0 Markus Volk
2023-09-21 14:42 ` Alexandre Belloni
2023-09-21 14:46 ` Alexander Kanavin
2023-09-21 21:04 ` Alexandre Belloni
2023-09-22 5:54 ` Alexander Kanavin
2023-09-21 20:59 ` Alexandre Belloni
2023-09-22 5:18 ` Alexander Kanavin
2023-09-22 6:42 ` Alexandre Belloni [this message]
2023-09-22 6:58 ` Alexander Kanavin
2023-09-22 9:44 ` Markus Volk
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=20230922064202279c2c00@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=f_l_k@t-online.de \
--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