Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Asselstine <mark.asselstine@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sdkext: use simpler kernel module for devtool test
Date: Wed, 21 Aug 2019 17:56:24 -0400	[thread overview]
Message-ID: <1770290.OrdOT5LAS6@yow-masselst-lx1> (raw)
In-Reply-To: <e6423f026434414f58509f3acec443d1cd681dfa.camel@linuxfoundation.org>

On Wednesday, August 21, 2019 4:57:40 P.M. EDT Richard Purdie wrote:
> On Tue, 2019-08-20 at 13:52 -0400, Mark Asselstine wrote:
> > The current devtool test for the building of an out-of-tree kernel
> > module uses something which requires several "high order" kconfigs to
> > be set. This results in the test failing, not for expected reasons,
> > but rather because it depends on specific kernel configuration.
> > 
> > You will get error messages such as
> > 
> >   ERROR: "video_ioctl2"
> >   [.../1.0-r5/testsdkext/workspace/sources/v4l2loopback-
> > 
> > driver/v4l2loopback.ko]
> > 
> >   undefined!
> >   ERROR: "video_unregister_device"
> >   [.../1.0-r5/testsdkext/workspace/sources/v4l2loopback-
> > 
> > driver/v4l2loopback.ko]
> > 
> >   undefined!
> > 
> > Using a simpler hello-world kernel module example will only require
> > that CONFIG_MODULE is enabled, thus avoiding a false positive.
> > 
> > Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
> > ---
> > 
> > Richard, it is unclear if I need to match this change in
> > meta/lib/oeqa/manual/crops.json.
> 
> Those are manual tests for crops. They probably do also need this
> change as it would make them more reliable if/as anyone every automates
> them, or runs them manually.

I will affect the change there then too in the V2.

> 
> >  Please let me know and I
> > 
> > send a V2 which does this. I am not fond of pointing at
> > my own github but it was the best option to ensure it will
> > exist and not be messed with.
> 
> The best option may be to put that repo onto git.yoctoproject.org?

Not sure I get a vote but as far as the content goes I have no issue with it 
being elsewhere, like git.yoctoproject.org.

Mark

> 
> Cheers,
> 
> Richard






      reply	other threads:[~2019-08-21 21:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 17:52 [PATCH] sdkext: use simpler kernel module for devtool test Mark Asselstine
2019-08-21 20:57 ` Richard Purdie
2019-08-21 21:56   ` Mark Asselstine [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=1770290.OrdOT5LAS6@yow-masselst-lx1 \
    --to=mark.asselstine@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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