All of lore.kernel.org
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: alexey kodanev <alexey.kodanev@oracle.com>,
	vasily isaenko <vasily.isaenko@oracle.com>,
	ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] fw_load: new test of device firmware loading
Date: Tue, 11 Jun 2013 14:37:14 +0200	[thread overview]
Message-ID: <20130611123714.GB8061@rei> (raw)
In-Reply-To: <716795963.1251428.1370952887038.JavaMail.root@redhat.com>

Hi!
> 
> Perhaps also:
> 0. if module fails to build, continue with rest of LTP build

Sure, that was in some of the mails as well but I omited it here since
the question was about what to to when the test is executed.

> > 
> > 1. Is there foo.ko?
> >    
> >    if not -> module wasn't build -> TCONF
> > 
> > 2. Try to insmod/modprobe module
> > 
> >    if failure -> most likely module not compatible with kernel -> TBROK
> > 
> > 3. do actual test
> > 
> > ...

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      parent reply	other threads:[~2013-06-11 12:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 12:06 [LTP] [PATCH] fw_load: new test of device firmware loading Alexey Kodanev
2013-06-05 15:37 ` Jan Stancek
2013-06-05 15:54   ` chrubis
2013-06-06 11:01     ` chrubis
     [not found]       ` <51B706F8.9070303@oracle.com>
2013-06-11 12:11         ` chrubis
     [not found]           ` <716795963.1251428.1370952887038.JavaMail.root@redhat.com>
2013-06-11 12:37             ` chrubis [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=20130611123714.GB8061@rei \
    --to=chrubis@suse.cz \
    --cc=alexey.kodanev@oracle.com \
    --cc=jstancek@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vasily.isaenko@oracle.com \
    /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.