From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 0/4] Pull request #21
Date: Thu, 1 Sep 2011 17:50:43 +0200 [thread overview]
Message-ID: <cover.1314892207.git.Martin.Jansa@gmail.com> (raw)
The following changes since commit a577b53823d5a0e078777a5fb56a1e3d776b3130:
lmbench: Add version 3.0-a9 (initial recipe) (2011-09-01 16:30:32 +0200)
are available in the git repository at:
git://git.openembedded.org/meta-openembedded-contrib jansa/meta-oe
http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=jansa/meta-oe
Martin Jansa (3):
kbd: fix SRC_URI
klibc: move comment outside multiline variable
serial-forward, pty-forward-native: remove extra slash and '.git'
from SRC_URI
Sebastian Krzyszkowiak (1):
xf86-video-omapfb: add patch for fixing segfault on starting X when
using VRFB
meta-oe/recipes-core/kbd/kbd_1.15.2.bb | 2 +-
meta-oe/recipes-devtools/klibc/klibc_1.5.24.bb | 2 +-
.../0004-Attempt-to-fix-VRFB.patch | 320 ++++++++++++++++++++
.../xorg-driver/xf86-video-omapfb_git.bb | 3 +-
.../serial-utils/pty-forward-native.bb | 2 +-
.../serial-utils/serial-forward_git.bb | 2 +-
6 files changed, 326 insertions(+), 5 deletions(-)
create mode 100644 meta-oe/recipes-graphics/xorg-driver/xf86-video-omapfb/0004-Attempt-to-fix-VRFB.patch
--
1.7.6.1
next reply other threads:[~2011-09-01 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 15:50 Martin Jansa [this message]
2011-09-01 15:50 ` [meta-oe][PATCH 1/4] kbd: fix SRC_URI Martin Jansa
2011-09-01 15:50 ` [meta-oe][PATCH 2/4] klibc: move comment outside multiline variable Martin Jansa
2011-09-01 15:50 ` [meta-oe][PATCH 3/4] serial-forward, pty-forward-native: remove extra slash and '.git' from SRC_URI Martin Jansa
2011-09-01 15:50 ` [meta-oe][PATCH 4/4] xf86-video-omapfb: add patch for fixing segfault on starting X when using VRFB Martin Jansa
2011-09-01 19:01 ` Eric Bénard
2011-09-02 7:16 ` Martin Jansa
2011-09-02 7:22 ` Eric Bénard
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.1314892207.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