From: Jan Stancek <jstancek@redhat.com>
To: Alexey Kodanev <alexey.kodanev@oracle.com>
Cc: vasily isaenko <vasily.isaenko@oracle.com>,
ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH v2] fw_load: new test of device firmware loading
Date: Fri, 14 Jun 2013 09:48:16 -0400 (EDT) [thread overview]
Message-ID: <104332332.3007867.1371217696167.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1371208652-25804-1-git-send-email-alexey.kodanev@oracle.com>
Hi,
I ran this on older kernel, which worked fine - it skipped the build.
Then I tried RHEL7 alpha, which has more recent kernel: 3.10.0-0.rc4,
but it failed:
# ./fw_load
cp: cannot stat ‘/lib/udev/rules.d/50-firmware.rules’: No such file or directory
fw_load 1 TBROK : Failed to copy '/lib/udev/rules.d/50-firmware.rules' to '/etc/udev/rules.d/' at fw_load.c:164
fw_load 2 TBROK : Remaining cases broken
fw_load 0 TWARN : tst_rmdir: TESTDIR was NULL; no removal attempted
I'll see if I can find out what happened to 50-firmware.rules,
it could some side-effect of systemd.
I found this initialization a little confusing, since your test
always relies on passing it from user-space (which passes 9):
> +static int fw_num = 8;
Regards,
Jan
------------------------------------------------------------------------------
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
next prev parent reply other threads:[~2013-06-14 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 11:17 [LTP] [PATCH v2] fw_load: new test of device firmware loading Alexey Kodanev
2013-06-14 13:48 ` Jan Stancek [this message]
2013-06-14 14:44 ` alexey.kodanev
2013-06-14 15:16 ` Jan Stancek
2013-06-17 8:39 ` alexey.kodanev
2013-06-17 8:50 ` Jan Stancek
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=104332332.3007867.1371217696167.JavaMail.root@redhat.com \
--to=jstancek@redhat.com \
--cc=alexey.kodanev@oracle.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.