From: Greg KH <greg@kroah•com>
To: Alexis Berlemont <alexis.berlemont@gmail•com>
Cc: linux-next@vger•kernel.org
Subject: Re: linux-next: comedi: Range_table and range_table_list
Date: Mon, 27 Apr 2009 08:25:08 -0700 [thread overview]
Message-ID: <20090427152508.GA23851@kroah.com> (raw)
In-Reply-To: <72cf3fb0904270137s4ac40211i8965ef0110fad7dd@mail.gmail.com>
On Mon, Apr 27, 2009 at 10:37:43AM +0200, Alexis Berlemont wrote:
> Hi,
>
> On Mon, Apr 27, 2009 at 4:38 AM, Greg KH <greg@kroah•com> wrote:
> > On Sun, Apr 26, 2009 at 11:47:51PM +0200, Alexis Berlemont wrote:
> >> Hi,
> >>
> >> Please, find attached two patches related with the Comedi layer.
> >
> > Can you resend this, and cc: the comedi developers at the same time so
> > that they can evaluate your change to the code?
>
> I already did so. As a matter of fact, I reached comedi's mailing list
> first. Here is the original thread:
> http://groups.google.com/group/comedi_list/browse_thread/thread/85be8195ddf52896
>
> Ian Abott told me that the original Comedi CVS tree will not integrate
> such a code change. He suggested me to redirect my mail to linux-next
> as the staging area is supposed to host any "cleanup effort".
Yes, the upstream comedi cvs tree is pretty much "gone" now, as all of
the comedi developers are working against the linux-next tree, as you
rightly did.
But, the discussion of the development still happens on the comedi
mailing list (and cc: me please if you want patches added). Not on the
linux-next mailing list, which is only for linux-next specific issues,
not general development stuff like this.
Hope this helps clear things up.
thanks,
greg k-h
prev parent reply other threads:[~2009-04-27 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 21:47 linux-next: comedi: Range_table and range_table_list Alexis Berlemont
2009-04-27 2:38 ` Greg KH
2009-04-27 4:55 ` Stephen Rothwell
2009-04-27 8:37 ` Alexis Berlemont
2009-04-27 9:56 ` Stephen Rothwell
2009-04-27 15:25 ` Greg KH
2009-04-27 15:25 ` Greg KH [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=20090427152508.GA23851@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=alexis.berlemont@gmail$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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