From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 7/9] linux-yocto: aufs and systemtap
Date: Wed, 14 Mar 2018 11:11:26 -0400 [thread overview]
Message-ID: <9f288566-afd0-c6d7-7481-c69b818f9c5c@windriver.com> (raw)
In-Reply-To: <CAJTo0LbY_61zJ=nCBGgmruLOY+x2Ky6Coj-D9X743iXBAFJ6+g@mail.gmail.com>
On 2018-03-14 8:50 AM, Burton, Ross wrote:
> On 14 March 2018 at 12:46, Bruce Ashfield <bruce.ashfield@windriver.com
> <mailto:bruce.ashfield@windriver.com>> wrote:
>
> I'll revert this for now (or see if I can quickly move it to a debug
> kernel build), and yes, there is a better way to do this. I'm just not
> sure I can get it done in time for the release.
>
>
> Thanks. I'm desperately trying to be able to tell RP we can fire the M3
> build so I'm +1 on reverting now, fixing later.
revert sent. I put all the details in the commit log about how
to build systemtap with the relevant options enabled. So there's
still a way to build with the options that were the intent of that
change, and with this revert the standard kernel should go back
to normal.
Bruce
>
> Ross
next prev parent reply other threads:[~2018-03-14 15:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 18:11 [PATCH 0/9] kernel-yocto: consolidated pull request Bruce Ashfield
2018-03-06 18:11 ` [PATCH 1/9 v3] kernel-devsrc: restructure for out of tree (and on target) module builds Bruce Ashfield
2018-03-07 8:40 ` Burton, Ross
2018-03-07 13:35 ` Bruce Ashfield
2018-03-08 18:51 ` Richard Purdie
2018-03-15 13:45 ` Bruce Ashfield
2018-03-29 13:30 ` Richard Purdie
2018-03-06 18:11 ` [PATCH 2/9] linux-libc-headers: update to 4.15.7 Bruce Ashfield
2018-03-06 18:11 ` [PATCH 3/9] linux-yocto/4.15: update to v4.15.7 Bruce Ashfield
2018-03-06 18:11 ` [PATCH 4/9] linux-yocto/4.14: update to v4.14.24 Bruce Ashfield
2018-03-06 18:11 ` [PATCH 5/9] linux-yocto/4.12: fix aufs compile warning Bruce Ashfield
2018-03-06 18:11 ` [PATCH 6/9] linux-yocto/4.12: memleak and build warning fixes Bruce Ashfield
2018-03-06 18:11 ` [PATCH 7/9] linux-yocto: aufs and systemtap Bruce Ashfield
2018-03-07 8:38 ` Burton, Ross
2018-03-07 13:39 ` Bruce Ashfield
2018-03-07 15:06 ` Bruce Ashfield
2018-03-07 15:35 ` Burton, Ross
2018-03-14 12:41 ` Burton, Ross
2018-03-14 12:46 ` Bruce Ashfield
2018-03-14 12:50 ` Burton, Ross
2018-03-14 15:11 ` Bruce Ashfield [this message]
2018-03-06 18:11 ` [PATCH 8/9] linux-yocto/4.12: warning: drm/i915/cfl: Coffee Lake works on Kaby Lake PCH Bruce Ashfield
2018-03-06 18:11 ` [PATCH 9/9] kernel: make copying of crtsavres.o conditional Bruce Ashfield
2018-03-06 18:33 ` ✗ patchtest: failure for kernel-yocto: consolidated 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=9f288566-afd0-c6d7-7481-c69b818f9c5c@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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