From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: openembedded-core@lists.openembedded.org, yocto@pengutronix.de,
Steve Sakoman <steve@sakoman.com>
Subject: Re: [OE-core] [PATCH] icecc: fix PN 'no-pn' handling
Date: Mon, 16 Dec 2024 22:33:12 +0000 [thread overview]
Message-ID: <63fd8df5142be2e4e87d390db461ea41584311ce.camel@linuxfoundation.org> (raw)
In-Reply-To: <20241216222221.ylk2ijte5h56ecsa@pengutronix.de>
On Mon, 2024-12-16 at 23:22 +0100, Marco Felsch wrote:
> Hi,
>
> On 24-12-16, Richard Purdie wrote:
> > On Mon, 2024-12-09 at 18:38 +0100, Marco Felsch wrote:
> > > On 24-12-09, Richard Purdie wrote:
> > > > On Mon, 2024-12-09 at 17:22 +0000, Richard Purdie via
> > > > lists.openembedded.org wrote:
>
> ...
>
> > > > The modern way of doing much of this would be a python prefunc
> > > > on
> > > > the
> > > > appropriate tasks. I have to wonder how many people are using
> > > > icecc
> > > > :/.
> > >
> > > Okay, I will give it a try with a python based prefunc.
> >
> > Just wanted to say thanks for that patch, it looks like a neater
> > way to
> > fix this and likely other issues too.
>
> I've seen that you applied both v2 patches onto the master branch. Is
> it possible to apply both to scarthgap too?
From my perspective I think they would be reasonable fixes to backport
given the relative isolation of the class and the benefit as they are
broken at the moment. I've copied Steve Sakoman on the email, you need
to point him at the patches. To save a few electrons, the patches in
question are:
https://git.yoctoproject.org/poky/commit/?id=f391bf2c0804aca812ad24e52c14b30347726111
https://git.yoctoproject.org/poky/commit/?id=b8e99c75a1b0c7c5bb84adcb907061005f504764
Cheers,
Richard
prev parent reply other threads:[~2024-12-16 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 16:46 [PATCH] icecc: fix PN 'no-pn' handling Marco Felsch
2024-12-09 17:22 ` [OE-core] " Richard Purdie
[not found] ` <180F920C983A7BC6.8554@lists.openembedded.org>
2024-12-09 17:25 ` Richard Purdie
2024-12-09 17:38 ` Marco Felsch
2024-12-16 17:02 ` Richard Purdie
2024-12-16 22:22 ` Marco Felsch
2024-12-16 22:33 ` 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=63fd8df5142be2e4e87d390db461ea41584311ce.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=m.felsch@pengutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.com \
--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