linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Aleksey Dashevsky <alekseyd@yahoo.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: 64-bit LUN support in Linux kernel?
Date: Mon, 25 Nov 2013 13:16:25 +0100	[thread overview]
Message-ID: <52933F99.7060300@suse.de> (raw)
In-Reply-To: <1385381014.92441.YahooMailNeo@web121101.mail.ne1.yahoo.com>

On 11/25/2013 01:03 PM, Aleksey Dashevsky wrote:
> Dear Hannes,
> 
> I'm wondering what happens to your patch set with Linux 64-bit LUN
> support? As far as I understand you'd got few more SCSI related
> patches in your drawer
> (http://www.spinics.net/lists/linux-scsi/msg69428.html), but they
> have been  pushed upstream recently.
> 
Currently I'm trying to excite any comment from James B. after the
latest respin of my eh-timeout patchset.
In _principle_ the patchset is now clean, and everyone agrees it
should get in. But as long as James B. doesn't react here I don't
see a point in sending my other patches, as they sort of rely on
each other.

Currently I have these patchsets queued:

- eh-timeout
- per-device logging level support
- 64-bit LUN support
- Further EH improvements:
  - remove duplicate hooks
  - move eh_host_reset_handler
    to take 'struct Scsi_Host' as argument,
  etc.

I was planning to send the per-device logging level support
in the next round, as this is touching quite a lot of areas,
but it's probably the most uncontroversial.
64-bit LUN support will be sent afterwards, as this needs some
modifications to the LLDDs, some of which cannot handle
64-bit LUNs without internal modifications. And I would need
to discuss with the vendors of how to handle these issues.

But then, as even the first patchset hasn't moved forward
in the recent weeks I fail to see the point in sending the others,
as I cannot be sure if and when the first one is getting in.

If there is interest I can put these patches up to my git
repository, of course.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
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

       reply	other threads:[~2013-11-25 12:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1385381014.92441.YahooMailNeo@web121101.mail.ne1.yahoo.com>
2013-11-25 12:16 ` Hannes Reinecke [this message]
     [not found]   ` <1385390632.22761.YahooMailNeo@web121104.mail.ne1.yahoo.com>
     [not found]     ` <1385645372.8003.YahooMailNeo@web121105.mail.ne1.yahoo.com>
2013-12-10 11:14       ` 64-bit LUN support in Linux kernel? Hannes Reinecke

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=52933F99.7060300@suse.de \
    --to=hare@suse.de \
    --cc=alekseyd@yahoo.com \
    --cc=linux-scsi@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 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).