From: Stephen Williams <steve@icarus.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [linux-usb-devel] hotplug remover support
Date: Wed, 06 Jun 2001 16:16:08 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-99184422609552@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99184320905882@msgid-missing>
> If they don't get integrated, then I'll choose to package and distribute
> my patch on my own, along with my application, at least until there is
> an adequate equivilent.
david-b@pacbell.net said:
> I thought Greg was going to integrate these...
Well, when I do a cvs diff (I have an anonymous copy) I don't see
any changes. Is this a sourceforge problem?
david-b@pacbell.net said:
> I'm also interested in seeing that firmware download support option
> get integrated. You had volunteered to put a version of your EZ-USB
> (original, FX, and FX2) firmware downloader into CVS and set up a new
> compiled C section in the hotplug project.
Sure. My offer still stands. I would probably use a common source rpm
that makes a core that is still noarch and a utils that has the other
add-on tools such as fxload.
I would rather let my previous patch get integrated first, so that I
don't wind up creating a backlog of unapplied patches.
--
Steve Williams "The woods are lovely, dark and deep.
steve@icarus.com But I have promises to keep,
steve@picturel.com and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-06-06 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 15:56 [linux-usb-devel] hotplug remover support David Brownell
2001-06-06 16:16 ` Stephen Williams [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=marc-linux-hotplug-99184422609552@msgid-missing \
--to=steve@icarus.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).