From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: make check error
Date: Tue, 30 Nov 2010 22:18:43 +0000 [thread overview]
Message-ID: <AANLkTi=oRpyL-qXZDw3VfpnuWBh8Hm6XtuHPRwV71AFR@mail.gmail.com> (raw)
In-Reply-To: <4CF56CDA.20308@gmail.com>
On Tue, Nov 30, 2010 at 22:30, robert <mullinrobert@gmail.com> wrote:
> TEST 142: magic [subsys/sysname] attribute substitution
> device
> '/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda'
> expecting node/link 'sda-8741C4G-end'
> permissions: ok
> add: ok
> remove: ok
>
> 1 errors occured
>
> FAIL: test/udev-test.pl
> =======================
> 1 of 1 test failed
> Please report to linux-hotplug@vger.kernel.org
> =======================
> make[3]: *** [check-TESTS] Error 1
> make[2]: *** [check-am] Error 2
> make[1]: *** [check-recursive] Error 1
> make: *** [check] Error 2
> root:/sources/udev-161# make check
Hmm, I can't reproduce that in current code.
Kay
prev parent reply other threads:[~2010-11-30 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 21:30 make check error robert
2010-11-30 22:18 ` Kay Sievers [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='AANLkTi=oRpyL-qXZDw3VfpnuWBh8Hm6XtuHPRwV71AFR@mail.gmail.com' \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).