From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alexis Berlemont <alexis.berlemont@gmail.com>,
linux-next@vger.kernel.org
Subject: Re: linux-next: comedi: Range_table and range_table_list
Date: Mon, 27 Apr 2009 08:25:57 -0700 [thread overview]
Message-ID: <20090427152557.GB23851@kroah.com> (raw)
In-Reply-To: <20090427195620.41376d41.sfr@canb.auug.org.au>
On Mon, Apr 27, 2009 at 07:56:20PM +1000, Stephen Rothwell wrote:
> 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?
The upstream comedi tree should now be "dead" as everything is now fed
into mainline and linux-next through staging. So everything should be
good.
thanks,
greg k-h
next 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 [this message]
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=20090427152557.GB23851@kroah.com \
--to=greg@kroah.com \
--cc=alexis.berlemont@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).