From: Greg KH <greg@kroah.com>
To: Alessio Igor Bogani <abogani@texware.it>
Cc: Ian Abbott <abbotti@mev.co.uk>,
Frank Mori Hess <fmhess@users.sourceforge.net>,
David Schleef <ds@schleef.org>,
LKML <linux-kernel@vger.kernel.org>,
Comedi-ml <comedi_list@googlegroups.com>
Subject: Re: RFC about Comedi on a patch that remove a lot fo code
Date: Fri, 24 Apr 2009 15:51:22 -0700 [thread overview]
Message-ID: <20090424225122.GB3343@kroah.com> (raw)
In-Reply-To: <63a49ef40904240228g6a28ba8dsf63d2e0bdc6b57d9@mail.gmail.com>
On Fri, Apr 24, 2009 at 11:28:28AM +0200, Alessio Igor Bogani wrote:
> Dear Comedi developers,
>
> Sorry for my bad english.
>
> I would be happy to receive your considerations about that patch:
>
> http://marc.info/?l=linux-next&m=123792129500760&w=2
>
> I know that some users use Comedi on dual kernel approach systems.
> Obviously I don't have any against this but i think that Linux git
> tree isn't the right place to support those software (RTAI, Xenomai,
> RTLinux and others). Those projects already released patches against
> Linux source code so it very easy for them add also patch for Comedi
> drivers in the same tarball.
>
> At the already listed 8 reasons in that email I want added a ninth one:
> 9) Give more chance for interested developers to fix it against RT_PREEMPT
> http://marc.info/?l=linux-rt-users&m=124049407712792&w=2
I am siding with you, and agree all of the RT stuff should be deleted
from the in-kernel comedi code, as there is on in-kernel users of it.
Also, the recent Linux RT changes will not need any of these
driver-specific changes at all from what I can tell, so they are now
obsolete.
Frank, unless you have any major objections, I'd like to remove this
code.
thanks,
greg k-h
next prev parent reply other threads:[~2009-04-24 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 9:28 RFC about Comedi on a patch that remove a lot fo code Alessio Igor Bogani
2009-04-24 22:51 ` Greg KH [this message]
2009-04-26 15:08 ` Frank Mori Hess
2009-04-28 22:56 ` 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=20090424225122.GB3343@kroah.com \
--to=greg@kroah.com \
--cc=abbotti@mev.co.uk \
--cc=abogani@texware.it \
--cc=comedi_list@googlegroups.com \
--cc=ds@schleef.org \
--cc=fmhess@users.sourceforge.net \
--cc=linux-kernel@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