On Tue, Sep 20, 2022 at 8:55 AM Richard Purdie
wrote:
>
> On Tue, 2022-09-20 at 08:53 -0400, Bruce Ashfield wrote:
> > On Tue, Sep 20, 2022 at 8:22 AM Richard Purdie
> > wrote:
> > >
> > > On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfi...@gmail.com wrote:
> > > > From: Bruce Ashfield
> > > >
> >
On Tue, 2022-09-20 at 08:53 -0400, Bruce Ashfield wrote:
> On Tue, Sep 20, 2022 at 8:22 AM Richard Purdie
> wrote:
> >
> > On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfi...@gmail.com wrote:
> > > From: Bruce Ashfield
> > >
> > > Richard,
> > >
> > > Here's the next set of -stable updates to th
On Tue, Sep 20, 2022 at 8:22 AM Richard Purdie
wrote:
>
> On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfi...@gmail.com wrote:
> > From: Bruce Ashfield
> >
> > Richard,
> >
> > Here's the next set of -stable updates to the active reference kernels.
> > I also have updates back to 5.4 that I'll send
On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfi...@gmail.com wrote:
> From: Bruce Ashfield
>
> Richard,
>
> Here's the next set of -stable updates to the active reference kernels.
> I also have updates back to 5.4 that I'll send to the various stable
> branches shortly.
>
> I also have a couple
On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfi...@gmail.com wrote:
> Here's the next set of -stable updates to the active reference kernels.
> I also have updates back to 5.4 that I'll send to the various stable
> branches shortly.
>
> I also have a couple of kern-tools fixes. One to solve a probl
On Mon, Sep 19, 2022 at 10:28 AM Bruce Ashfield
wrote:
>
> From: Bruce Ashfield
>
> Richard,
>
> Here's the next set of -stable updates to the active reference kernels.
> I also have updates back to 5.4 that I'll send to the various stable
> branches shortly.
>
> I also have a couple of kern-tool
From: Bruce Ashfield
Richard,
Here's the next set of -stable updates to the active reference kernels.
I also have updates back to 5.4 that I'll send to the various stable
branches shortly.
I also have a couple of kern-tools fixes. One to solve a problem reported
on the list about some directory
From: Bruce Ashfield
Richard,
Here are the gathered changes for our active lnux-yocto references, as well
as some pre-work for moving to 5.13+ as the reference. I've also included
a patch to add some BSP/SRC_URI information after the kernel meta data has
been gathered .. this was requested just
On Thu, Feb 6, 2020 at 4:03 AM Richard Purdie
wrote:
>
> Hi Bruce,
>
> On Wed, 2020-02-05 at 18:12 -0500, bruce.ashfi...@gmail.com wrote:
> > From: Bruce Ashfield
> >
> > Hi all,
> >
> > I've kept the v5.4 content changes, as well as the kernel version
> > default
> > changes out of this series a
Hi Bruce,
On Wed, 2020-02-05 at 18:12 -0500, bruce.ashfi...@gmail.com wrote:
> From: Bruce Ashfield
>
> Hi all,
>
> I've kept the v5.4 content changes, as well as the kernel version
> default
> changes out of this series and instead focused it on the collection
> of
> kernel-yocto and kern-tool
From: Bruce Ashfield
Hi all,
I've kept the v5.4 content changes, as well as the kernel version default
changes out of this series and instead focused it on the collection of
kernel-yocto and kern-tools tweaks that I've gethered over the past few
weeks.
I have Martin's gold linker fixes included
Hi all,
Here is my queue of changes for kernel-yocto.
These are mainly -stable updates, but contained in those updates are the gcc8
fixes that we need to get gcc8 working for the reference kernels in master.
I've also fixed a couple of issues that were found in the last
4.12 update.
Note: I'll
Hi all,
This is the latest consolidated kernel pull request. It contains -stable
updates,
the kernel-devsrc re-work, and a libc-headers version bump.
The -stable updates are routine, and are required to pick up the latest CVE and
bug fixes from korg.
The kernel-devsrc re-structure has already g
Hi all,
This is the last set of -stable and meta data changes for the 2.4
release window. I've also brough aufs4 into the 4.12 tree to keep
it feature consistent with all the previous linux-yocto kernels
(and given some bug reports, folks are using the aufs support).
They are -stable updates, som
On Tue, 2017-08-22 at 16:34 -0400, Bruce Ashfield wrote:
> On 08/22/2017 12:07 PM, Richard Purdie wrote:
> I found the commit that is causing the problem (after three hours
> of bisecting). That's the good news. The bad news is it isn't
> something
> I can revert .. or easily fix, since the commit
On 08/22/2017 12:07 PM, Richard Purdie wrote:
On Tue, 2017-08-22 at 12:04 -0400, Bruce Ashfield wrote:
On 08/22/2017 12:00 PM, Richard Purdie wrote:
On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
I can send you a v4 of the 4.12 patch in the next half an hour,
that's easiest for me
On 08/22/2017 12:07 PM, Richard Purdie wrote:
On Tue, 2017-08-22 at 12:04 -0400, Bruce Ashfield wrote:
On 08/22/2017 12:00 PM, Richard Purdie wrote:
On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
I can send you a v4 of the 4.12 patch in the next half an hour,
that's easiest for me
On 08/22/2017 12:07 PM, Richard Purdie wrote:
On Tue, 2017-08-22 at 12:04 -0400, Bruce Ashfield wrote:
On 08/22/2017 12:00 PM, Richard Purdie wrote:
On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
I can send you a v4 of the 4.12 patch in the next half an hour,
that's easiest for me
On Tue, 2017-08-22 at 12:04 -0400, Bruce Ashfield wrote:
> On 08/22/2017 12:00 PM, Richard Purdie wrote:
> >
> > On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
> > >
> > > I can send you a v4 of the 4.12 patch in the next half an hour,
> > > that's easiest for me to do.
> > >
> > > ..
On 08/22/2017 12:00 PM, Richard Purdie wrote:
On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
I can send you a v4 of the 4.12 patch in the next half an hour,
that's easiest for me to do.
.. but if it isn't for you, go ahead and do the merge and I'll
sort it out in a follow up.
The ab
On Tue, 2017-08-22 at 11:34 -0400, Bruce Ashfield wrote:
> I can send you a v4 of the 4.12 patch in the next half an hour,
> that's easiest for me to do.
>
> .. but if it isn't for you, go ahead and do the merge and I'll
> sort it out in a follow up.
The above works, I'm still trying to get to th
On 08/22/2017 11:28 AM, Richard Purdie wrote:
On Tue, 2017-08-22 at 10:54 -0400, Bruce Ashfield wrote:
On 08/22/2017 10:24 AM, Richard Purdie wrote:
Thanks, I think you got that one but the /bin/awk issue remained
after
your changes. Its easy to reproduce with "bitbake core-image-sato-
sdk",
On Tue, 2017-08-22 at 10:54 -0400, Bruce Ashfield wrote:
> On 08/22/2017 10:24 AM, Richard Purdie wrote:
> >
> > Thanks, I think you got that one but the /bin/awk issue remained
> > after
> > your changes. Its easy to reproduce with "bitbake core-image-sato-
> > sdk",
> > or IMAGE_INSTALL_append =
On 08/22/2017 10:24 AM, Richard Purdie wrote:
On Mon, 2017-08-21 at 12:12 -0400, Bruce Ashfield wrote:
On 2017-08-21 11:55 AM, Richard Purdie wrote:
On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
Here's the collected set of kernel changes that are ready for the
M3
builds.
We have
On Mon, 2017-08-21 at 12:12 -0400, Bruce Ashfield wrote:
> On 2017-08-21 11:55 AM, Richard Purdie wrote:
> >
> > On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> > >
> > > Here's the collected set of kernel changes that are ready for the
> > > M3
> > > builds.
> > >
> > > We have some
On 2017-08-21 11:55 AM, Richard Purdie wrote:
On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
Here's the collected set of kernel changes that are ready for the M3
builds.
We have some kernel meta data changes:
kernel-yocto: configuration updates: x86 features
linux-yocto/4.1: fi
On 2017-08-21 11:55 AM, Richard Purdie wrote:
On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
Here's the collected set of kernel changes that are ready for the M3
builds.
We have some kernel meta data changes:
kernel-yocto: configuration updates: x86 features
linux-yocto/4.1: fi
On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> Here's the collected set of kernel changes that are ready for the M3
> builds.
>
> We have some kernel meta data changes:
>
> kernel-yocto: configuration updates: x86 features
> linux-yocto/4.1: fix fsl-ls10xx sdhci
> linux-yocto: a
On Mon, Aug 21, 2017 at 8:11 AM, Bruce Ashfield
wrote:
>
>
> On Mon, Aug 21, 2017 at 7:42 AM, Richard Purdie <
> richard.pur...@linuxfoundation.org> wrote:
>
>> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
>> > Hi all,
>> >
>> > Here's the collected set of kernel changes that are read
On Mon, Aug 21, 2017 at 7:42 AM, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> > Hi all,
> >
> > Here's the collected set of kernel changes that are ready for the M3
> > builds.
> >
> > We have some kernel meta data changes
On Sun, 2017-08-20 at 22:58 -0400, Bruce Ashfield wrote:
> Hi all,
>
> Here's the collected set of kernel changes that are ready for the M3
> builds.
>
> We have some kernel meta data changes:
>
> kernel-yocto: configuration updates: x86 features
> linux-yocto/4.1: fix fsl-ls10xx sdhci
> l
Hi all,
Here's the collected set of kernel changes that are ready for the M3 builds.
We have some kernel meta data changes:
kernel-yocto: configuration updates: x86 features
linux-yocto/4.1: fix fsl-ls10xx sdhci
linux-yocto: add usb-net configs by default
Some bug fixes:
kernel-yocto:
32 matches
Mail list logo
