From: "André Draszik" <git@andred.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 0/3] fixing kernel module cross-recipe dependency
Date: Mon, 05 Sep 2016 12:18:23 +0100 [thread overview]
Message-ID: <1473074303.17211.13.camel@andred.net> (raw)
In-Reply-To: <1472207936.19220.11.camel@andred.net>
On Fr, 2016-08-26 at 11:38 +0100, André Draszik wrote:
> On Do, 2016-08-18 at 08:56 +0100, André Draszik wrote:
> >
> > In a situation where multiple external kernel modules are built
> > from multiple independent recipes, we currently don't generate
> > correct runtime dependencies of the packages created.
> >
> > This (small) series of patches attempts to address this.
>
> Is there anything wrong with these patches?
I don't want to be rude, just in case this series ended up under the radar,
I'm asking again :-)
a.
prev parent reply other threads:[~2016-09-05 11:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 15:25 [PATCH 0/2] fixing kernel module cross-recipe dependency André Draszik
2016-08-17 15:25 ` [PATCH 1/2] module.bbclass: use Module.symvers for dependants André Draszik
2016-08-17 15:25 ` [PATCH 2/2] kernel-module-split.bbclass: generate dependencies across recipes André Draszik
2016-08-17 16:12 ` [PATCH] kernel-module-split.bbclass: no need for running depmod André Draszik
2016-08-18 7:56 ` [PATCH v2 0/3] fixing kernel module cross-recipe dependency André Draszik
2016-08-18 7:56 ` [PATCH v2 1/3] module.bbclass: use Module.symvers for dependants André Draszik
2016-11-16 20:18 ` Denys Dmytriyenko
2016-11-17 10:22 ` André Draszik
2016-11-17 18:47 ` Denys Dmytriyenko
2016-08-18 7:56 ` [PATCH v2 2/3] kernel-module-split.bbclass: generate dependencies across recipes André Draszik
2016-08-18 7:56 ` [PATCH v2 3/3] kernel-module-split.bbclass: no need for running depmod André Draszik
2016-08-26 10:38 ` [PATCH v2 0/3] fixing kernel module cross-recipe dependency André Draszik
2016-09-05 11:18 ` André Draszik [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=1473074303.17211.13.camel@andred.net \
--to=git@andred.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.