From: "Rusty Lynch" <rusty@linux.co.intel.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug Test Cases or Test Procedures
Date: Wed, 20 Nov 2002 05:01:37 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-103776860910671@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-103775851104322@msgid-missing>
----- Original Message -----
From: "Greg KH" <greg@kroah.com>
To: "Rusty Lynch" <rusty@linux.co.intel.com>
Cc: <Linux-hotplug-devel@lists.sourceforge.net>
Sent: Tuesday, November 19, 2002 6:47 PM
Subject: Re: Hotplug Test Cases or Test Procedures
> On Tue, Nov 19, 2002 at 06:10:29PM -0800, Rusty Lynch wrote:
> > I have a couple of people that have been tasked to start testing the
> > CompactPCI hotplug implementation for a couple of platforms, and was
> > wondering if there was an existing test case or test procedure
> > repository for the hotplug project.
>
> Yeah, testers! :)
>
> No, there aren't any published test procedures that I know of. I know a
> number of different companies have some private ones that they have used
> to test their specific drivers, but so far, I have not been able to
> convince anyone of them to make them public.
>
> > From poking around the web site I didn't stumble across anything, but
> > it wouldn't be the first time I missed the obvious.
>
> Um, don't confuse the linux-hotplug project with the PCI hotplug
> project. They are two different things (but the PCI hotplug code relies
> on the linux-hotplug userspace code to load any needed modules, so they
> are intertwined a bit).
>
Yeap, I'm mixing up the projects. Although I'm betting that the test
procedures will end up covering both.
> > If there is no such thing, where would people like to see such
> > contributions? At the very least, this would consist of a few text
> > documents that detailed step by step manual procedures for a tester to
> > validate the latest bits on some platform.
>
> That would be great, I would love to have this for my use alone in
> testing new code out.
>
> > Would this be something people would like to see in the hotplug CVS
> > repository?
>
> Um, maybe in the pci hotplug cvs repository, if you really want to use
> CVS. Or we can just put it up on the web site.
Writing the procedures as html and making them accessable via the web site
sounds like a good way to start.
>
> > Maybe I could approach the LTP?
>
> Traditionally they have only wanted tests that they can automate, and
> unfortunately, pci hotplug tests (and most driver tests) can't be
> automated very easily. But it can't hurt to try asking them :)
I'll ping the LTP people to see if they are interested, but that shouldn't
slow us down any.
>
> thanks,
>
> greg k-h
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: To learn the basics of securing
> your web site with SSL, click here to get a FREE TRIAL of a Thawte
> Server Certificate: http://www.gothawte.com/rd524.html
> _______________________________________________
> Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
> Linux-hotplug-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2002-11-20 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-20 2:10 Hotplug Test Cases or Test Procedures Rusty Lynch
2002-11-20 2:47 ` Greg KH
2002-11-20 5:01 ` Rusty Lynch [this message]
2002-11-20 8:33 ` David Brownell
2002-11-20 17:30 ` Rusty Lynch
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=marc-linux-hotplug-103776860910671@msgid-missing \
--to=rusty@linux.co.intel.com \
--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).