On Tue, Jul 17, 2012 at 02:17:22PM -0700, Nicholas A. Bellinger wrote:
Wrt to staging, I'd like to avoid mucking with staging because:
*) The code has been posted for review
*) The code has been converted to use the latest target-core primitives
*) The code does not require cleanups between staging -> merge
*) The code has been stable the last 7 days since RFC-v2 with heavy
BTW I don't suggest putting code itself in staging. Just the config
flag to enable it. Once we are more or less sure multiple userspaces
are using this driver, we'll move the config hopefully already in 3.7.
What's the downside?
--
MST
On Wed, 2012-07-18 at 00:58 +0300, Michael S. Tsirkin wrote:
On Tue, Jul 17, 2012 at 02:17:22PM -0700, Nicholas A. Bellinger wrote:
quoted
Wrt to staging, I'd like to avoid mucking with staging because:
*) The code has been posted for review
*) The code has been converted to use the latest target-core primitives
*) The code does not require cleanups between staging -> merge
*) The code has been stable the last 7 days since RFC-v2 with heavy
BTW I don't suggest putting code itself in staging. Just the config
flag to enable it. Once we are more or less sure multiple userspaces
are using this driver, we'll move the config hopefully already in 3.7.
What's the downside?
Ahh, sorry I managed to miss that part.. ;)
If it's just a CONFIG_STAGING flag for a release or two until we work
out the userspace bits, I don't have an objection doing something like
that if it helps getting the code exposed to a large set of eyes in
mainline.
--nab