From: Paul Barker <paul@betafive.co.uk>
To: "Andreas Müller" <schnitzeltony@gmail.com>
Cc: bruce.ashfield@windriver.com,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: kernel menuconfig broken?
Date: Sat, 14 Apr 2018 10:10:14 +0100 [thread overview]
Message-ID: <20180414101014.4bcbbc31@host0.betafive.co.uk> (raw)
In-Reply-To: <CALbNGRQT94ptEPAygj+Rm9vBm27yo=inbz+O6nR2gL_etkGd7g@mail.gmail.com>
On Fri, 13 Apr 2018 00:12:16 +0200
Andreas Müller <schnitzeltony@gmail.com> wrote:
> On Thu, Apr 12, 2018 at 11:46 PM, Andreas Müller
> <schnitzeltony@gmail.com> wrote:
> > On Thu, Apr 12, 2018 at 11:38 PM, Cal Sullivan
> > <california.l.sullivan@intel.com> wrote:
> >> If you're using a non-linux-yocto kernel you likely need to apply this patch
> >> to your kernel as well:
> >>
> >> https://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/recipes-kernel/linux/linux-intel/0001-menuconfig-check-lxdiaglog.sh-Allow-specification-of.patch
> > Correct: RaspberryPi kernel
> >>
> >> (This is in all linux-yocto kernels, I'm only linking to meta-intel because
> >> I knew where it was off the top of my head)
> >>
> >> This was sent upstream but last I looked it didn't gain any traction. I
> >> think Bruce resent it recently but I can't be sure.
> >>
> >> Thanks,
> >> Cal
> >>
> > That looks very promising - will try and let you know - thanks in advance :)
> >
> Perfect! - Thanks Cal for quick help!
Sounds like we should apply this to the kernel recipe in
meta-raspberrypi.
Andreas, want to send a PR for this? Or shall I add to my todo list?
Cheers,
--
Paul Barker
Beta Five Ltd
next prev parent reply other threads:[~2018-04-14 9:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 21:49 kernel menuconfig broken? Andreas Müller
2018-04-02 21:57 ` Trevor Woerner
2018-04-12 20:28 ` Andreas Müller
2018-04-12 21:19 ` Cal Sullivan
2018-04-12 21:29 ` Andreas Müller
2018-04-12 21:38 ` Cal Sullivan
2018-04-12 21:46 ` Andreas Müller
2018-04-12 22:12 ` Andreas Müller
2018-04-14 9:10 ` Paul Barker [this message]
2018-04-14 12:55 ` Andreas Müller
2018-04-14 18:42 ` Trevor Woerner
2018-04-14 19:06 ` Andreas Müller
2018-09-21 10:04 ` Andreas Müller
2018-09-21 11:46 ` Anuj Mittal
2018-09-21 12:31 ` Bruce Ashfield
2018-09-21 14:39 ` Andreas Müller
2018-09-21 15:33 ` Andreas Müller
2018-09-21 15:34 ` Bruce Ashfield
2018-09-21 15:57 ` Bruce Ashfield
2018-04-13 19:54 ` 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=20180414101014.4bcbbc31@host0.betafive.co.uk \
--to=paul@betafive.co.uk \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=schnitzeltony@gmail.com \
/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