From: tom.zanussi@intel.com
To: bruce.ashfield@windriver.com, yocto@yoctoproject.org
Subject: [PATCH 0/8][KERNEL] some meta-intel bsp cleanup, v4
Date: Sun, 9 Oct 2011 22:34:44 -0500 [thread overview]
Message-ID: <cover.1318217109.git.tom.zanussi@intel.com> (raw)
From: Tom Zanussi <tom.zanussi@intel.com>
This patchset is another step in some cleanup I'm doing for
the meta-intel bsps, basically removing unneeded or redundant
options and abstracting out useful features, in this case a
new vesafb feature used in this patchset by crownbay, emenlow,
and jasperforest.
This patchset doesn't change any of the previous patches - I'm
just resending them all to avoid confusion since I accidentally
named the v2 branch v3. So this patchset keeps everything
up-to-date and supersedes the previous "v2" patchset.
v2: rebased on top of intervening changes
v3: misnamed
v4: added fishriver, sugarbay, fri2
Please pull into linux-yocto-3.0.
Pull URL: git://git.pokylinux.org/linux-yocto-2.6.37-contrib
Branch: tzanussi/bsp-cleanup-v4
Browse: http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=tzanussi/bsp-cleanup-v4
Thanks,
Tom
Tom Zanussi (8):
features/drm-psb: add related config options
meta: add vesafb feature
crownbay: cleanup bsp config
emenlow: cleanup bsp config
jasperforest: cleanup bsp config
fishriver: cleanup bsp config
sugarbay: cleanup bsp config
fri2: cleanup bsp config
meta/cfg/kernel-cache/bsp/crownbay/crownbay.cfg | 34 ++++--------------
meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc | 5 ++-
meta/cfg/kernel-cache/bsp/emenlow/emenlow.cfg | 35 +++++--------------
meta/cfg/kernel-cache/bsp/emenlow/emenlow.scc | 2 +
meta/cfg/kernel-cache/bsp/fishriver/fishriver.cfg | 34 ++++--------------
meta/cfg/kernel-cache/bsp/fishriver/fishriver.scc | 2 +
meta/cfg/kernel-cache/bsp/fri2/fri2.cfg | 34 ++++--------------
meta/cfg/kernel-cache/bsp/fri2/fri2.scc | 2 +
.../kernel-cache/bsp/jasperforest/jasperforest.cfg | 7 +---
.../kernel-cache/bsp/jasperforest/jasperforest.scc | 2 +
meta/cfg/kernel-cache/bsp/sugarbay/sugarbay.cfg | 22 +-----------
meta/cfg/kernel-cache/bsp/sugarbay/sugarbay.scc | 1 +
meta/cfg/kernel-cache/features/drm-psb/drm-psb.cfg | 13 +++++++
.../kernel-cache/features/framebuffer/vesafb.cfg | 8 ++++
.../kernel-cache/features/framebuffer/vesafb.scc | 1 +
15 files changed, 71 insertions(+), 131 deletions(-)
create mode 100644 meta/cfg/kernel-cache/features/framebuffer/vesafb.cfg
create mode 100644 meta/cfg/kernel-cache/features/framebuffer/vesafb.scc
next reply other threads:[~2011-10-10 3:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 3:34 tom.zanussi [this message]
2011-10-10 3:34 ` [PATCH 1/8][KERNEL] features/drm-psb: add related config options tom.zanussi
2011-10-10 3:34 ` [PATCH 2/8][KERNEL] meta: add vesafb feature tom.zanussi
2011-10-10 3:34 ` [PATCH 3/8][KERNEL] crownbay: cleanup bsp config tom.zanussi
2011-10-10 3:34 ` [PATCH 4/8][KERNEL] emenlow: " tom.zanussi
2011-10-10 3:34 ` [PATCH 5/8][KERNEL] jasperforest: " tom.zanussi
2011-10-10 3:34 ` [PATCH 6/8][KERNEL] fishriver: " tom.zanussi
2011-10-10 3:34 ` [PATCH 7/8][KERNEL] sugarbay: " tom.zanussi
2011-10-10 3:34 ` [PATCH 8/8][KERNEL] fri2: " tom.zanussi
2011-10-10 14:14 ` [PATCH 0/8][KERNEL] some meta-intel bsp cleanup, v4 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.1318217109.git.tom.zanussi@intel.com \
--to=tom.zanussi@intel.com \
--cc=bruce.ashfield@windriver.com \
--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.