From: Adrian Bunk <bunk@stusta.de>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/8] kernel-devsrc: remove python2 dependency
Date: Thu, 29 Aug 2019 15:53:51 +0300 [thread overview]
Message-ID: <20190829125351.GB32705@localhost> (raw)
In-Reply-To: <CADkTA4NXYy0jnZg6=S_W=3znH9M1hidYw8MDwqOqQCGESq8p=g@mail.gmail.com>
On Thu, Aug 29, 2019 at 08:23:58AM -0400, Bruce Ashfield wrote:
> On Thu, Aug 29, 2019 at 2:32 AM Adrian Bunk <bunk@stusta.de> wrote:
> >
> > On Wed, Aug 28, 2019 at 06:06:04PM -0400, Bruce Ashfield wrote:
> > > On Wed, Aug 28, 2019 at 5:58 PM Adrian Bunk <bunk@stusta.de> wrote:
> > > >
> > > > On Wed, Aug 28, 2019 at 04:11:43PM -0400, Bruce Ashfield wrote:
> > > > >...
> > > > > There's zero risk to these, and no reason to sit on them.
> > > >
> > > > What range of LTS kernels is covered by the "zero risk"?
> > >
> > > It has nothing to do with LTS kernels.
>...
> > How do your changes interact with a BSP layer that provides
> > the upstream maintained LTS kernel 4.4?
>
> As mentioned in other parts of the threads, we test against the
> reference kernel's in master. Other versions can either bbappend, or
> send patches. That's unfortunately how it has to be.
It is an unexpected meaning of "zero risk" when this excludes
breakages with kernels other than the ones in master.
One of the non-python changes to perf blew up the build for me even when
trying with a kernel that is only a few months behind on the 4.19 branch,
so there's some patches for me to send next month.
> Cheers,
>
> Bruce
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-08-29 12:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 19:28 [PATCH 0/8] kernel/kernel-yocto: consolidated M3 feature pull request bruce.ashfield
2019-08-28 19:28 ` [PATCH 1/8] linux-libc-headers: update to v5.2 headers bruce.ashfield
2019-08-28 19:28 ` [PATCH 2/8] linux-yocto: introduce 5.2 recipes bruce.ashfield
2019-08-28 20:00 ` Adrian Bunk
2019-08-28 20:06 ` Bruce Ashfield
2019-08-28 19:28 ` [PATCH 3/8] bluez5: fix build against libc-headers 5.2+ bruce.ashfield
2019-08-28 19:28 ` [PATCH 4/8] kernel-devsrc: remove python2 dependency bruce.ashfield
2019-08-28 20:05 ` Adrian Bunk
2019-08-28 20:11 ` Bruce Ashfield
2019-08-28 21:58 ` Adrian Bunk
2019-08-28 22:06 ` Bruce Ashfield
2019-08-29 6:31 ` Adrian Bunk
2019-08-29 12:23 ` Bruce Ashfield
2019-08-29 12:53 ` Adrian Bunk [this message]
2019-08-29 13:00 ` Alexander Kanavin
2019-08-28 20:12 ` richard.purdie
2019-08-28 20:57 ` Alexander Kanavin
2019-08-28 19:28 ` [PATCH 5/8] perf: change dependencies on python to python3 bruce.ashfield
2019-08-29 0:01 ` Mittal, Anuj
2019-08-29 0:13 ` Bruce Ashfield
2019-08-29 0:18 ` Mittal, Anuj
2019-08-29 0:24 ` Bruce Ashfield
2019-08-29 0:27 ` Bruce Ashfield
2019-08-29 1:08 ` Bruce Ashfield
2019-08-28 19:28 ` [PATCH 6/8] perf: v5.3+ build fixes bruce.ashfield
2019-08-29 0:32 ` Bruce Ashfield
2019-08-29 1:45 ` Bruce Ashfield
2019-08-28 19:28 ` [PATCH 7/8] devsrc: update arm64 scripts/prepare for kernels 5.3+ bruce.ashfield
2019-08-28 19:28 ` [PATCH 8/8] qemu: bump linux-yocto preferred version to 5.2 bruce.ashfield
2019-08-28 19:33 ` ✗ patchtest: failure for kernel/kernel-yocto: consolidated M3 feature pull request Patchwork
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=20190829125351.GB32705@localhost \
--to=bunk@stusta.de \
--cc=bruce.ashfield@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.