On Mon, Dec 05 2022, Richard Purdie wrote:
> On Mon, 2022-12-05 at 11:00 +0100, Ola x Nilsson wrote:
>> On Wed, Nov 30 2022, Richard Purdie wrote:
>>
>> > On Wed, 2022-11-30 at 17:56 +0100, Alexandre Belloni wrote:
>> > > On 30/11/2022 16:46:17+, Ross Burton wrote:
>> > > > On 30 Nov 2022,
On Mon, 2022-12-05 at 11:00 +0100, Ola x Nilsson wrote:
> On Wed, Nov 30 2022, Richard Purdie wrote:
>
> > On Wed, 2022-11-30 at 17:56 +0100, Alexandre Belloni wrote:
> > > On 30/11/2022 16:46:17+, Ross Burton wrote:
> > > > On 30 Nov 2022, at 14:20, Richard Purdie via
> > > >
On Wed, Nov 30 2022, Richard Purdie wrote:
> On Wed, 2022-11-30 at 17:56 +0100, Alexandre Belloni wrote:
>> On 30/11/2022 16:46:17+, Ross Burton wrote:
>> > On 30 Nov 2022, at 14:20, Richard Purdie via
>> > lists.yoctoproject.org
>> > wrote:
>> > > > > * Could we optionally disable some of
On Thu, 2022-12-01 at 11:27 +0100, Alexander Kanavin wrote:
> On Wed, 30 Nov 2022 at 14:15, Richard Purdie
> wrote:
> > * We need to have a 32 bit ptest run on the autobuilder (qemux86 should
> > work, not sure we can make qemuarm fast). Whether this is manually
> > triggered, not sure. We could
On Wed, 30 Nov 2022 at 14:15, Richard Purdie
wrote:
> * We need to have a 32 bit ptest run on the autobuilder (qemux86 should
> work, not sure we can make qemuarm fast). Whether this is manually
> triggered, not sure. We could have a smaller set of ptests to run for
> it?
I just ran qemux86 full
On Wed, 2022-11-30 at 17:56 +0100, Alexandre Belloni wrote:
> On 30/11/2022 16:46:17+, Ross Burton wrote:
> > On 30 Nov 2022, at 14:20, Richard Purdie via lists.yoctoproject.org
> > wrote:
> > > > > * Could we optionally disable some of the glibc 32 bit function calls
> > > > > to ensure
On 30/11/2022 16:46:17+, Ross Burton wrote:
> On 30 Nov 2022, at 14:20, Richard Purdie via lists.yoctoproject.org
> wrote:
> >>> * Could we optionally disable some of the glibc 32 bit function calls
> >>> to ensure they're not being used?
> >>
> >> Could you be more specific here? Would
On 30 Nov 2022, at 14:20, Richard Purdie via lists.yoctoproject.org
wrote:
>>> * Could we optionally disable some of the glibc 32 bit function calls
>>> to ensure they're not being used?
>>
>> Could you be more specific here? Would you like to disable some
>> syscalls?
>
> I'm meaning
On Wed, Nov 30, 2022 at 12:08 AM Alexander Kanavin
wrote:
>
> On Tue, 29 Nov 2022 at 16:45, Stephen Jolley wrote:
> > We’d welcome a proposal/series on how to move forward with the Y2038 work
> > for 32 bit platforms.
>
> I have the following proposal:
>
> 1. A branch is made where:
> a.
On Wed, 2022-11-30 at 14:36 +0100, Lukasz Majewski wrote:
> > On Wed, 2022-11-30 at 09:07 +0100, Alexander Kanavin wrote:
> > > On Tue, 29 Nov 2022 at 16:45, Stephen Jolley
> > > wrote:
> > > > We’d welcome a proposal/series on how to move forward with the
> > > > Y2038 work for 32 bit
Hi Richard,
> On Wed, 2022-11-30 at 09:07 +0100, Alexander Kanavin wrote:
> > On Tue, 29 Nov 2022 at 16:45, Stephen Jolley
> > wrote:
> > > We’d welcome a proposal/series on how to move forward with the
> > > Y2038 work for 32 bit platforms.
> >
> > I have the following proposal:
> >
> >
On Wed, 2022-11-30 at 09:07 +0100, Alexander Kanavin wrote:
> On Tue, 29 Nov 2022 at 16:45, Stephen Jolley wrote:
> > We’d welcome a proposal/series on how to move forward with the Y2038 work
> > for 32 bit platforms.
>
> I have the following proposal:
>
> 1. A branch is made where:
> a.
12 matches
Mail list logo
