LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Richard Holden <aciddeath@gmail.com>
To: "J.R. Mauro" <jrm8005@gmail.com>
Cc: "Moritz Muehlenhoff" <jmm@debian.org>,
linux-kernel@vger.kernel.org, "Greg KH" <gregkh@suse.de>
Subject: Re: staging: me4000 and relation to other data acquisition devices
Date: Wed, 29 Oct 2008 18:46:10 -0600 [thread overview]
Message-ID: <0246BB7A-4217-4309-898E-FFD6D42424C2@gmail.com> (raw)
In-Reply-To: <3aaafc130810291737i41716bd2r767150b47239b0a1@mail.gmail.com>
On Oct 29, 2008, at 6:37 PM, J.R. Mauro wrote:
> On Wed, Oct 29, 2008 at 2:57 PM, Moritz Muehlenhoff <jmm@debian.org>
> wrote:
>> Greg KH wrote:
>>> Of course, if someone doesn't want their code in the staging tree, I
>>> will not add it, that's just being "nice".
>>>
>>> As for what I will not put into staging, right now I'm sticking with
>>> drivers only, no filesystems (people have asked already). I don't
>>> think
>>> we have seen any drivers that I will not put into the staging tree
>>> yet.
>>
>> Hi Greg,
>> Great effort with staging, thanks a lot!
>>
>> I've had a look at the out-of-tree kernel drivers currently present
>> in Debian, maybe you want to merge some into staging. The Debian
>> overview pages contain download links (the orig.tar.gz files):
>>
>> Voicetronix telephony hardware:
>> http://packages.qa.debian.org/v/vpb-driver.html
>> http://www.voicetronix.com.au/
>>
I'm working on the Quicknet IXJ driver currently and I could take this
driver too if it would help.
>> Cheers,
>> Moritz
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-
>> kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>
> Greg,
>
> If you're interested in having the above drivers get into staging and
> need someone to email the developers about it, I humbly volunteer.
>
> ~J.R.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-
> kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
I guess I just volunteered to maintain the telephony drivers, though
I'm still getting used to git. I'll send a Maintainers patch later
today.
-Richard Holden
next prev parent reply other threads:[~2008-10-30 0:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 15:49 Shawn Bohrer
2008-10-28 16:34 ` Greg KH
2008-10-28 17:33 ` Randy Dunlap
2008-10-28 18:14 ` Greg KH
2008-10-29 15:12 ` Wolfgang Beiter
2008-10-30 0:02 ` Greg KH
2008-10-29 18:57 ` Moritz Muehlenhoff
2008-10-30 0:37 ` J.R. Mauro
2008-10-30 0:46 ` Richard Holden [this message]
2008-10-30 1:42 ` Greg KH
2008-10-30 14:25 ` J.R. Mauro
2008-10-30 15:23 ` Greg KH
2008-10-30 15:42 ` J.R. Mauro
2008-10-31 15:00 ` Greg KH
2008-10-31 15:10 ` J.R. Mauro
2008-10-30 1:43 ` Greg KH
2008-10-29 17:37 ` Shawn Bohrer
2008-10-30 0:04 ` Greg KH
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=0246BB7A-4217-4309-898E-FFD6D42424C2@gmail.com \
--to=aciddeath@gmail.com \
--cc=gregkh@suse.de \
--cc=jmm@debian.org \
--cc=jrm8005@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: staging: me4000 and relation to other data acquisition devices' \
/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
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).