From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alexis Berlemont <alexis.berlemont@gmail•com>
Cc: Greg KH <greg@kroah•com>, linux-next@vger•kernel.org
Subject: Re: linux-next: comedi: Range_table and range_table_list
Date: Mon, 27 Apr 2009 19:56:20 +1000 [thread overview]
Message-ID: <20090427195620.41376d41.sfr@canb.auug.org.au> (raw)
In-Reply-To: <72cf3fb0904270137s4ac40211i8965ef0110fad7dd@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
Hi ALexis,
On Mon, 27 Apr 2009 10:37:43 +0200 Alexis Berlemont <alexis.berlemont@gmail•com> wrote:
>
> 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".
He is mistaken about linux-next: no development work goes on there, just
integration testing. All staging tree work needs to be directed to Greg
(as this was).
Also, are we going to have problems if the original developers of things
in the staging tree are unwilling to take updates back into their trees?
Or is this just a procedural thing i.e. do they only want things fed back
after they have been in the staging tree? Will this change if their work
ends up in the kernel proper?
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-27 9:56 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 [this message]
2009-04-27 15:25 ` Greg KH
2009-04-27 15:25 ` 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=20090427195620.41376d41.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alexis.berlemont@gmail$(echo .)com \
--cc=greg@kroah$(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