public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "richard.purdie@linuxfoundation.org"
	<richard.purdie@linuxfoundation.org>,
	"bruce.ashfield@gmail.com" <bruce.ashfield@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"bluelightning@bluelightning.org"
	<bluelightning@bluelightning.org>
Subject: Re: [OE-core] [PATCH 0/8] linux-yocto: consolidated pull requesrt
Date: Mon, 21 Dec 2020 02:57:22 +0000	[thread overview]
Message-ID: <cf65e19893f23bd5987ec4d50904e45838ad68d0.camel@intel.com> (raw)
In-Reply-To: <faff0743666a4ef199d2902a1611a83ee5c2a4a9.camel@linuxfoundation.org>

Hi Bruce,

On Sat, 2020-12-19 at 11:31 +0000, Richard Purdie 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

I think this would need:

https://git.yoctoproject.org/cgit/cgit.cgi/yocto-kernel-cache/commit/features/firmware?id=1bde5ac3c3b324853958c24513a6a949d09138bc

to be included in v5.4 branch as well. But I am wondering why is it
being flagged now. I can't figure out what has changed ...

Thanks,

Anuj

> 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.
> 
> Cheers,
> 
> Richard
> 
> 
> 
> 


  parent reply	other threads:[~2020-12-21  2:57 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
2020-12-19 16:04       ` Bruce Ashfield
2020-12-21  2:57   ` Anuj Mittal [this message]
2020-12-21  3:34     ` [OE-core] " 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=cf65e19893f23bd5987ec4d50904e45838ad68d0.camel@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=bluelightning@bluelightning.org \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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