seeing couple of build failure in meta-oe too
https://errors.yoctoproject.org/Errors/Build/172283/
On Sun, Oct 1, 2023 at 10:40 AM Khem Raj wrote:
>
> On Sun, Oct 1, 2023 at 4:49 AM Richard Purdie
> wrote:
> >
> > On Sun, 2023-10-01 at 11:13 +0100, Richard Purdie wrote:
> > > On Fri, 2023-09-2
On Sun, Oct 1, 2023 at 4:49 AM Richard Purdie
wrote:
>
> On Sun, 2023-10-01 at 11:13 +0100, Richard Purdie wrote:
> > On Fri, 2023-09-29 at 16:04 -0400, bruce.ashfi...@gmail.com wrote:
> > > Given where we are in the release cycle, this clearly is NOT a typical
> > > consolidated pull request.
> >
On Sun, Oct 1, 2023 at 10:58 AM Bruce Ashfield
wrote:
>
>
> On Sun, Oct 1, 2023 at 7:49 AM Richard Purdie <
> richard.pur...@linuxfoundation.org> wrote:
>
>> On Sun, 2023-10-01 at 11:13 +0100, Richard Purdie wrote:
>> > On Fri, 2023-09-29 at 16:04 -0400, bruce.ashfi...@gmail.com wrote:
>> > > Giv
On Sun, Oct 1, 2023 at 7:49 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Sun, 2023-10-01 at 11:13 +0100, Richard Purdie wrote:
> > On Fri, 2023-09-29 at 16:04 -0400, bruce.ashfi...@gmail.com wrote:
> > > Given where we are in the release cycle, this clearly is NOT a typical
On Sun, 2023-10-01 at 11:13 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Fri, 2023-09-29 at 16:04 -0400, bruce.ashfi...@gmail.com wrote:
> > Given where we are in the release cycle, this clearly is NOT a typical
> > consolidated pull request.
> >
> > I've done what normally takes a
On Sun, 2023-10-01 at 11:13 +0100, Richard Purdie wrote:
> On Fri, 2023-09-29 at 16:04 -0400, bruce.ashfi...@gmail.com wrote:
> > Given where we are in the release cycle, this clearly is NOT a typical
> > consolidated pull request.
> >
> > I've done what normally takes about three weeks in about 4
On Fri, 2023-09-29 at 16:04 -0400, bruce.ashfi...@gmail.com wrote:
> Given where we are in the release cycle, this clearly is NOT a typical
> consolidated pull request.
>
> I've done what normally takes about three weeks in about 4 days.
>
> With 6.4 going EOL before expected upstream, it really
On Sat, 2023-09-30 at 13:05 -0400, Bruce Ashfield wrote:
> On Sat, Sep 30, 2023 at 12:58 PM Richard Purdie
> wrote:
> > On Sat, 2023-09-30 at 12:33 -0400, Bruce Ashfield wrote:
> > > On Sat, Sep 30, 2023 at 7:07 AM Richard Purdie
> > > wrote:
> > >
> > > >
> > > > I had some difficulties with t
On Sat, Sep 30, 2023 at 12:58 PM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Sat, 2023-09-30 at 12:33 -0400, Bruce Ashfield wrote:
> > On Sat, Sep 30, 2023 at 7:07 AM Richard Purdie
> > wrote:
> >
> > >
> > > I had some difficulties with this series since it doesn't apply
> >
On Sat, 2023-09-30 at 12:33 -0400, Bruce Ashfield wrote:
> On Sat, Sep 30, 2023 at 7:07 AM Richard Purdie
> wrote:
>
> >
> > I had some difficulties with this series since it doesn't apply
> > against
> > master. The issue was that someone else had updated the kernel CVEs
> > and
> > those chang
On Sat, Sep 30, 2023 at 7:07 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> Hi Bruce,
>
> On Fri, 2023-09-29 at 16:04 -0400, bruce.ashfi...@gmail.com wrote:
> > Given where we are in the release cycle, this clearly is NOT a typical
> > consolidated pull request.
> >
> > I've done
Hi Bruce,
On Fri, 2023-09-29 at 16:04 -0400, bruce.ashfi...@gmail.com wrote:
> Given where we are in the release cycle, this clearly is NOT a typical
> consolidated pull request.
>
> I've done what normally takes about three weeks in about 4 days.
Thanks, I know this isn't where any of us wanted
From: Bruce Ashfield
Richard,
Given where we are in the release cycle, this clearly is NOT a typical
consolidated pull request.
I've done what normally takes about three weeks in about 4 days.
With 6.4 going EOL before expected upstream, it really isn't a suitable
reference kernel for the rele
Hello Bruce,
It seems this series makes an efutils ptest fail:
backtrace: No modules recognized in core file
backtrace-child-core.18977: no main
rmdir: failed to remove 'test-18969': Directory not empty
FAIL: run-backtrace-native-core.sh
I guess something changed in the core generation.
On 15/1
From: Bruce Ashfield
Richard,
Here's the batched up -stable and -dev updates that I've been testing
for a while.
I've included both the 6.0 and 6.1 dev kernel updates, as both were
tested, and someone might want to use v6.0 as a development kernel,
and could use that commit as a baseline.
I ra
On Tue, 2022-01-11 at 12:59 -0500, bruce.ashfi...@gmail.com wrote:
> From: Bruce Ashfield
>
> Richard,
>
> Here's my next consolidated pull request. The -stable updates are
> routine, but I've included the default version bumps and dropping
> of 5.14 in this series.
>
> My AB run showed some pi
On Tue, Jan 11, 2022 at 3:47 PM Ross Burton wrote:
>
> Does this include the defconfig patches I sent earlier today, or will
> those need to wait for the next update?
Next update, but I'm doing the -stable updates from this past weekend
now, so they'll be following along very shortly.
Bruce
>
>
Does this include the defconfig patches I sent earlier today, or will
those need to wait for the next update?
Ross
On Tue, 11 Jan 2022 at 18:00, Bruce Ashfield wrote:
>
> From: Bruce Ashfield
>
> Richard,
>
> Here's my next consolidated pull request. The -stable updates are
> routine, but I've
From: Bruce Ashfield
Richard,
Here's my next consolidated pull request. The -stable updates are
routine, but I've included the default version bumps and dropping
of 5.14 in this series.
My AB run showed some ping/ssh failures on sato, but I haven't
reproduced them locally. So I wanted to send t
From: Bruce Ashfield
Richard,
Here's the -stable and bug fixes that I've been sitting on while hardknott went
through the final steps of release.
I've been building these locally without issue, so I don't expect much trouble.
I've also put the kern-tools change back into the queue that caused
20 matches
Mail list logo
