From: Christoph Hellwig <hch@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: "Wangshen (C)" <peter.w@huawei.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Jinbo (Justin)" <jinbo@huawei.com>
Subject: Re: Is there any plan to support 64bit lun in mainline?
Date: Mon, 14 Oct 2013 08:29:50 -0700 [thread overview]
Message-ID: <20131014152950.GA6625@infradead.org> (raw)
In-Reply-To: <525BC836.2030306@suse.de>
On Mon, Oct 14, 2013 at 12:32:22PM +0200, Hannes Reinecke wrote:
> However, there are two other patchsets pending (EH Deadline and
> asynchronous command aborts), both of which have been tested
> thoroughly _and_ have acked-by from various other parties.
> None of these patchset had received any feedback from James
> Bottomley, let alone any indication if or when they'll be merged.
>
> So I stopped sending further patchsets, sensing some communication
> breakdown on the line.
Maybe we'll need to start a common scsi staging tree for all patches
that have gotten a wide amount of reviews and are interesting to many
parties. Thay way we have one common set of patches for the
distributions to pull from, and a tree to develop against where
dependencies between the patchsets exist.
next prev parent reply other threads:[~2013-10-14 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 6:35 Is there any plan to support 64bit lun in mainline? Wangshen (C)
2013-10-14 10:32 ` Hannes Reinecke
2013-10-14 15:29 ` Christoph Hellwig [this message]
2013-10-20 16:20 ` Douglas Gilbert
2013-10-14 18:30 ` James Bottomley
2013-10-15 6:01 ` Hannes Reinecke
2013-10-15 14:58 ` James Bottomley
2013-10-16 4:11 ` Vladislav Bolkhovitin
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=20131014152950.GA6625@infradead.org \
--to=hch@infradead.org \
--cc=hare@suse.de \
--cc=jinbo@huawei.com \
--cc=linux-scsi@vger.kernel.org \
--cc=peter.w@huawei.com \
/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