All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Henzl <thenzl@redhat.com>
To: Christoph Hellwig <hch@lst.de>,
	lsf@lists.linux-foundation.org,
	lsf-pc@lists.linux-foundation.org, linux-scsi@vger.kernel.org
Subject: Re: [TOPIC] scsi-queue tree past and future
Date: Tue, 10 Mar 2015 13:37:05 +0100	[thread overview]
Message-ID: <54FEE571.6020909@redhat.com> (raw)
In-Reply-To: <20150305133118.GA16575@lst.de>

On 03/05/2015 02:31 PM, Christoph Hellwig wrote:
> For about 8 month I've merged almost every scsi commit through the
> scsi-queue staging tree, and it seems to have worked out well enough.

>From my user perspective the scsi-queue was an important help and have been using using
it a lot. I hope it will have a future.

Thanks,
Tomas

>
> I've been too busy for the next cycle, so 4.1 will probably have to live
> without it.  I'd like to get feedback on how the tree worked for contributors
> and driver maintainers, and brainstorm how to move forward with it, preferably
> some form of real team maintainance that avoids single points of failure.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      parent reply	other threads:[~2015-03-10 12:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 13:31 [TOPIC] scsi-queue tree past and future Christoph Hellwig
2015-03-05 14:48 ` James Bottomley
2015-03-07  4:22   ` [Lsf] " Davidlohr Bueso
2015-03-07  4:43     ` James Bottomley
2015-03-07  4:47       ` Davidlohr Bueso
2015-03-07  3:10 ` Sagi Grimberg
2015-03-10 12:37 ` Tomas Henzl [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=54FEE571.6020909@redhat.com \
    --to=thenzl@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=lsf@lists.linux-foundation.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.