From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-handheld][PATCH 0/2] kernel upgrade and PRINC fix
Date: Wed, 28 Mar 2012 13:53:07 +0200 [thread overview]
Message-ID: <cover.1332935553.git.Martin.Jansa@gmail.com> (raw)
The following changes since commit 1a1d50a1bf39136a8c974022d63e0f119f23bbff:
keymaps: edit script to reuse 2.6 kernel keymaps (2012-03-25 23:51:03 +0100)
are available in the git repository at:
git://gitorious.org/shr/meta-handheld jansa/pull
Martin Jansa (2):
linux-3.2: upgrade to 3.2.12
formfactor, keymaps, udev: use better form of PRINC
recipes-bsp/formfactor/formfactor_0.0.bbappend | 2 +-
recipes-bsp/keymaps/keymaps_1.0.bbappend | 2 +-
recipes-core/udev/udev_173.bbappend | 2 +-
recipes-kernel/linux/linux_3.2.bb | 8 ++++----
4 files changed, 7 insertions(+), 7 deletions(-)
--
1.7.8.5
next reply other threads:[~2012-03-28 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 11:53 Martin Jansa [this message]
2012-03-28 11:53 ` [meta-handheld][PATCH 1/2] linux-3.2: upgrade to 3.2.12 Martin Jansa
2012-03-28 11:53 ` [meta-handheld][PATCH 2/2] formfactor, keymaps, udev: use better form of PRINC Martin Jansa
2012-03-28 22:34 ` [meta-handheld][PATCH 0/2] kernel upgrade and PRINC fix Paul Eggleton
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.1332935553.git.Martin.Jansa@gmail.com \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox