From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Paul Eggleton <bluelightning@bluelightning.org>
Subject: Re: [PATCH 0/8] linux-yocto: consolidated pull requesrt
Date: Sat, 19 Dec 2020 15:52:05 +0000 [thread overview]
Message-ID: <f213eac0f84b71359c5909a54b45d4783574e836.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4Ou33v4AhB+JTTwxytUr1-UWRrbS8qd562utkiq-a49HQ@mail.gmail.com>
On Sat, 2020-12-19 at 10:48 -0500, Bruce Ashfield wrote:
> On Sat, Dec 19, 2020 at 6:31 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > Hi Bruce,
> >
> > On Mon, 2020-12-14 at 10:09 -0500, bruce.ashfield@gmail.com wrote:
> > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > >
> > > 5.10 dropped this morning, so I'm switching over to the libc-headers
> > > and reference kernel upgrade (5.4 and 5.10 will be in master, with
> > > 5.8 being dropped).
> > >
> > > But since that will take a bit to sort out, I wanted to send my queue
> > > of patches for other fixes/versions.
> > >
> > > I didn't pick up any issues with local testing, so hopefully this
> > > won't
> > > cause any problems.
> > >
> > > I have the lttng-modules patch from a previous send repeated here,
> > > since
> > > it may be easier to take it as part of the bulk update. I checked
> > > just a few minutes ago, and there isn't a new tagged version of the
> > > modules yet, so we still need the backported patches for 5.10+
> > > builds.
> >
> > I was able to merge part of the series but there were some warnings
> > that came up:
> >
> > meta-intel:
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/100/builds/1020
> > poky-tiny:
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/3105
> >
> > so I've deferred the kernel tooling bit until we can figure these out.
> > That means several other patches which depended on that also couldn't
> > make it in.
>
> Nothing else should have depended on the kern-tools ones, it is independent
> of the rest. Either way, I'll submit next week!
The others don't rebase cleanly without it and I wasn't sure if
resolving the rejects was going to be a good or a bad idea so I replied
on list and asked :)
Its probably easier for us both if I wait but I can rebase if it makes
sense.
Cheers,
Richard
next prev parent reply other threads:[~2020-12-19 15:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 15:09 [PATCH 0/8] linux-yocto: consolidated pull requesrt Bruce Ashfield
2020-12-14 15:09 ` [PATCH 1/8] linux-yocto-rt/5.4: update to -rt44 Bruce Ashfield
2020-12-14 15:09 ` [PATCH 2/8] linux-yocto/5.4: update to v5.4.80 Bruce Ashfield
2020-12-14 15:09 ` [PATCH 3/8] kern-tools: non-gcc config support and option re-classification Bruce Ashfield
2020-12-14 15:09 ` [PATCH 4/8] linux-yocto/cfg: qemuppc: set CONFIG_SCSI to '=y' Bruce Ashfield
2020-12-14 15:09 ` [PATCH 5/8] linux-yocto/5.4: update to v5.4.82 Bruce Ashfield
2020-12-14 15:09 ` [PATCH 6/8] linux-yocto/cfg: qemuarm64-gfx.cfg: add CONFIG_INPUT_UINPUT Bruce Ashfield
2020-12-14 15:09 ` [PATCH 7/8] lttng-modules: fix build against v5.10+ Bruce Ashfield
2020-12-14 15:09 ` [PATCH 8/8] linux-yocto/5.4: update to v5.4.83 Bruce Ashfield
2020-12-19 11:31 ` [PATCH 0/8] linux-yocto: consolidated pull requesrt Richard Purdie
2020-12-19 15:48 ` Bruce Ashfield
2020-12-19 15:52 ` Richard Purdie [this message]
2020-12-19 16:04 ` Bruce Ashfield
2020-12-21 2:57 ` [OE-core] " Anuj Mittal
2020-12-21 3:34 ` Bruce Ashfield
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=f213eac0f84b71359c5909a54b45d4783574e836.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bluelightning@bluelightning.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox