From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Kmod fixes
Date: Wed, 09 May 2012 21:12:46 -0700 [thread overview]
Message-ID: <4FAB403E.7040700@linux.intel.com> (raw)
In-Reply-To: <cover.1336517492.git.raj.khem@gmail.com>
On 05/08/2012 03:53 PM, Khem Raj wrote:
> This patchset fixes upgrade paths form kmod
> Updates to .8 release that should fix meta-oe PR being ahead of oe-core
> Packages libkmod in base_libdir instead of libdir
>
> The following changes since commit 043871d7e5d2d19c2ff43e54d2ff180c09e8903e:
>
> kern-tools: integrate minor fixes (2012-05-08 16:06:15 +0100)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib kraj/kmod
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/kmod
>
> Khem Raj (2):
> kmod: Update to .8 release
> kmod: Use base_libdir for installing libkmod
>
> Martin Jansa (1):
> kmod: fix upgrade path from module-init-tools
>
> meta/recipes-kernel/kmod/kmod.inc | 4 ++--
> meta/recipes-kernel/kmod/kmod_git.bb | 12 ++++++++----
> 2 files changed, 10 insertions(+), 6 deletions(-)
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-05-10 4:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 22:53 [PATCH 0/3] Kmod fixes Khem Raj
2012-05-08 22:53 ` [PATCH 1/3] kmod: fix upgrade path from module-init-tools Khem Raj
2012-05-08 22:53 ` [PATCH 2/3] kmod: Update to .8 release Khem Raj
2012-05-09 5:31 ` Koen Kooi
2012-05-09 9:42 ` Martin Jansa
2012-05-09 15:42 ` Khem Raj
2012-05-09 16:28 ` Koen Kooi
2012-05-09 18:49 ` Khem Raj
2012-05-08 22:53 ` [PATCH 3/3] kmod: Use base_libdir for installing libkmod Khem Raj
2012-05-11 12:47 ` Koen Kooi
2012-05-10 4:12 ` Saul Wold [this message]
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=4FAB403E.7040700@linux.intel.com \
--to=sgw@linux.intel.com \
--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.