All of lore.kernel.org
 help / color / mirror / Atom feed
From: devzero@web.de
To: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>,
	Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [GIT PULL] block updates for 2.6.32-rc
Date: Thu, 01 Oct 2009 01:25:36 +0200	[thread overview]
Message-ID: <935466370@web.de> (raw)

>> Hi Linus,
>> 
>> This looks huge, but it's mostly a cciss driver update and the addition
>> of drbd. I would have submitted this before -rc1, but Plumbers got in
>> the way.
>
>And DRBD is defintively not ready.  Even if people want to merge another
>duplicate RAID driver including another crappy user interface it has
>tracing stuff of a form that would let Ingo go beserk and also uses the
>stupid connector.

so, if DRBD is too ugly to be merged, i wonder why it`s not put in staging 
then before other kernel devs find yet another reason for not merging it 
at all. if they want it to be cleaned up, they can do it there or they can 
make the driver maintainer do it. or they can do it together. or they can 
let just sit it there until greg complains :)

all in all, it`s better than letting brilliant things like these live outside the
kernel tree. (which is more than 8 yrs now for DRBD)

What the Linux Staging tree is
The Linux Staging tree (or just "staging" from now on) is used to hold 
stand-alone drivers and filesystems that are not ready to be merged into 
the main portion of the Linux kernel tree at this point in time for various 
technical reasons. It is contained within the main Linux kernel tree so that 
users can get access to the drivers much easier than before, and to provide 
a common place for the development to happen, resolving the "hundreds 
of different download sites" problem that most out-of-tree drivers have had 
in the past.

( taken from http://www.kroah.com/log/linux/linux-staging-update.html )




______________________________________________________
GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://movieflat.web.de


             reply	other threads:[~2009-09-30 23:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 23:25 devzero [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-09-30 17:41 [GIT PULL] block updates for 2.6.32-rc Jens Axboe
2009-09-30 19:39 ` Christoph Hellwig
2009-10-01  7:05   ` Jens Axboe
2009-10-01  9:23     ` Lars Ellenberg
2009-10-01 18:44 ` Linus Torvalds
2009-10-01 18:59   ` Jens Axboe

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=935466370@web.de \
    --to=devzero@web.de \
    --cc=hch@infradead.org \
    --cc=jens.axboe@oracle.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.