Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] linux-yocto/4.4: updated pull request
Date: Mon, 7 Mar 2016 23:33:56 -0500	[thread overview]
Message-ID: <cover.1457411284.git.bruce.ashfield@windriver.com> (raw)

Hi all,

Ross pointed out that the AB found some issues with lttng when the refactored
kernel types change was included (missing modules).

I previously sent patch [linux-yocto/kernel-meta: ktype refactoring: move DEBUG_KERNEL,
EXPERT and EMBEDDED], and I've included it in this updated pull
request, but it is unchanged.

The new parts are a backport for wilwifi stability, and a patch that fixes up
the tracing configuration of the "production" kernel type.

I thought about squashing the ftrace fixup, with the refactored patch, but
keeping them separate is better in the history .. since it highlights some of
the issues when we rely on default/selected values.

Cheers,

Bruce

The following changes since commit 5ac3dc76a5afc2ed35b1abfc8e330e0c580eadf0:

  image.bbclass: fix incomplete .rootfs customization (2016-03-07 22:10:54 +0000)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (3):
  linux-yocto/kernel-meta: ktype refactoring: move DEBUG_KERNEL, EXPERT  and EMBEDDED
  linux-yocto/4.4: iwlwifi: mvm: don't allow sched scans without matches to be started
  linux-yocto/4.4: explicitly enable ftrace in tracing fragment

 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_4.4.bb      | 18 +++++++++---------
 3 files changed, 13 insertions(+), 13 deletions(-)

-- 
2.5.0



             reply	other threads:[~2016-03-08  4:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08  4:33 Bruce Ashfield [this message]
2016-03-08  4:33 ` [PATCH 1/3] linux-yocto/kernel-meta: ktype refactoring: move DEBUG_KERNEL, EXPERT and EMBEDDED Bruce Ashfield
2016-03-08  4:33 ` [PATCH 2/3] linux-yocto/4.4: iwlwifi: mvm: don't allow sched scans without matches to be started Bruce Ashfield
2016-03-08  4:33 ` [PATCH 3/3] linux-yocto/4.4: explicitly enable ftrace in tracing fragment 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=cover.1457411284.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.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