From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: module.init-tools-3.16.tar.bz2 no longer available at kernel.org
Date: Tue, 31 Jan 2012 11:26:18 -0800 [thread overview]
Message-ID: <4F28405A.7090902@linux.intel.com> (raw)
In-Reply-To: <CAMKF1sqhkRdWYDuHwq_4tSgdwvskBSLe94o5DTUnK6BzPZG7Cw@mail.gmail.com>
On 01/31/2012 12:58 AM, Khem Raj wrote:
> On Mon, Jan 30, 2012 at 11:57 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>>
>> Like the one in meta-oe? http://cgit.openembedded.org/meta-openembedded/commit/?id=2292ac565c220f2112a07abd563c6a9ee34dc662
>
> slightly better ;) Since I was intending to replace complete
> module-init-tools (including cross recipes) with kmod.
>
> have a look at top 3 patches on
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/misc-fixes
Hi Khem,
For kmod-cross and kmod-native, I thought the agreed upon PR bump method
was something like:
PR := "${@int(INC_PR) + 1}"
Was it not?
kmod.inc does "gtkdocize --docdir....", but I don't see a DEPENDS to
ensure gtkdocize exists.
Looking forward to seeing these in oe-core.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-01-31 19:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 7:41 module.init-tools-3.16.tar.bz2 no longer available at kernel.org Ulf Samuelsson
2012-01-29 10:21 ` Khem Raj
2012-01-29 12:23 ` Ulf Samuelsson
2012-01-30 7:52 ` Samuel Stirtzel
2012-01-30 15:27 ` Khem Raj
2012-01-31 1:50 ` Ni Qingliang
2012-01-31 4:24 ` Khem Raj
2012-01-31 7:57 ` Koen Kooi
2012-01-31 8:58 ` Khem Raj
2012-01-31 19:26 ` Darren Hart [this message]
2012-01-31 22:57 ` Khem Raj
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=4F28405A.7090902@linux.intel.com \
--to=dvhart@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox