From: "Wold, Saul" <saul.wold@intel.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH] systemtap: Bump SRCREV for 4.12 Linux kernel support
Date: Tue, 5 Sep 2017 21:26:07 +0000 [thread overview]
Message-ID: <1504646766.16957.13.camel@intel.com> (raw)
In-Reply-To: <20170905202254.31830-1-sgw@linux.intel.com>
On Tue, 2017-09-05 at 13:22 -0700, Saul Wold wrote:
> This SRCREV bump brings in support for the 4.12 Linux Kernel, this
> kernel
> also has some newer CONFIG settings. The newer DEBUG_INFO and
> DEBUG_INFO_DWARF4
> settings can be used with systemtap to get the full information. We
> do not
> normally enabled these for a 'production' (standard) kernel, but can
> be
> enabled via menuconfig.
>
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
Put a hold on this patch, I found an issue with a partial failure
during the install phase which did not cause an error to be thrown so
it completed!
Sau!
> ---
> meta/recipes-kernel/systemtap/systemtap_git.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/systemtap/systemtap_git.inc
> b/meta/recipes-kernel/systemtap/systemtap_git.inc
> index a6aedd38a6..ea2d2c0d1d 100644
> --- a/meta/recipes-kernel/systemtap/systemtap_git.inc
> +++ b/meta/recipes-kernel/systemtap/systemtap_git.inc
> @@ -1,6 +1,6 @@
> LICENSE = "GPLv2"
> LIC_FILES_CHKSUM =
> "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> -SRCREV = "b8ea350dc13adb6190d9044a5b80110a4c441270"
> +SRCREV = "45d0e7a09a15a21078d0ebf2db5175ed9e87014e"
> PV = "3.1"
>
> SRC_URI = "git://sourceware.org/git/systemtap.git \
> --
> 2.11.0
>
prev parent reply other threads:[~2017-09-05 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 20:22 [PATCH] systemtap: Bump SRCREV for 4.12 Linux kernel support Saul Wold
2017-09-05 21:26 ` Wold, Saul [this message]
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=1504646766.16957.13.camel@intel.com \
--to=saul.wold@intel.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