From: Darren Hart <dvhart@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>,
Darren Hart <dvhart@linux.intel.com>
Subject: [PATCH 0/1][meta-ti] linux-omap: cleanup and wl1271 build fix
Date: Mon, 6 Jun 2011 15:50:05 -0700 [thread overview]
Message-ID: <cover.1307400276.git.dvhart@linux.intel.com> (raw)
This adds two patches cleaning up whitespace and fixing a build issue with
the iwl12xx expansionboard initialization. These do not apply to the linux-omap
tree directly, and need to be pushed along with the rest of the patches
currently residing in the linux-omap directory.
The following changes since commit cb3d37c30fa71afeda8127e963965542f0171471:
linux-omap4: sync with OE .dev (2011-05-09 11:57:55 +0200)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib dvhart/beagleboard
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=dvhart/beagleboard
Darren Hart (1):
beagleboard: cleanup board-omap3beagle.c and allow for building
without wl1271
...0001-board-omap3beagle-whitespace-cleanup.patch | 91 ++++++++++++++++++++
...3beagle-allow-for-building-without-wl1271.patch | 42 +++++++++
recipes-bsp/linux/linux-omap_2.6.37.bb | 2 +
3 files changed, 135 insertions(+), 0 deletions(-)
create mode 100644 recipes-bsp/linux/linux-omap/0001-board-omap3beagle-whitespace-cleanup.patch
create mode 100644 recipes-bsp/linux/linux-omap/0002-board-omap3beagle-allow-for-building-without-wl1271.patch
next reply other threads:[~2011-06-06 22:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 22:50 Darren Hart [this message]
2011-06-06 22:50 ` [PATCH 1/1] beagleboard: cleanup board-omap3beagle.c and allow for building without wl1271 Darren Hart
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.1307400276.git.dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.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.