From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: dvhart@linux.intel.com, poky@yoctoproject.org, yocto@yoctoproject.org
Subject: [PATCH 0/2] linux-yocto/meta: update kernel meta-data
Date: Fri, 1 Apr 2011 23:26:38 -0400 [thread overview]
Message-ID: <cover.1301714584.git.bruce.ashfield@windriver.com> (raw)
Richard,
patch 1 in this series is a re-send of a previous change, since
it was still on the queue and it was worth keeping it in history
in order with the second change.
The second patch addresses [YOCTO #945], and the patch itself
has the following:
[
As part of the update to 2.6.37 existing configuration and
patches from the -stable kernel were left in place as a reminder
of features and configuration carry forward. A lot of these
reminders are no longer necessary and the kernel meta data
needs to be cleaned up to prepare for activities related to
newer kernels.
Also in this meta update are configuration changes to allow
common_pc derived BSPs to have a clean baseline configuration.
]
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: zedd/kernel
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Thanks,
Bruce Ashfield <bruce.ashfield@windriver.com>
---
Bruce Ashfield (2):
linux-yocto/crownbay: update configuration
linux-yocto/meta: cleanup and streamline kernel meta data
.../conf/distro/include/poky-default-revisions.inc | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
next reply other threads:[~2011-04-02 3:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-02 3:26 Bruce Ashfield [this message]
2011-04-02 3:26 ` [PATCH 1/2] linux-yocto/crownbay: update configuration Bruce Ashfield
2011-04-02 3:26 ` [PATCH 2/2] linux-yocto/meta: cleanup and streamline kernel meta data Bruce Ashfield
2011-04-04 12:58 ` [PATCH 0/2] linux-yocto/meta: update kernel meta-data Richard Purdie
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.1301714584.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.