From: Hannes Reinecke <hare@suse.de>
To: Tejun Heo <tj@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
James Bottomley <jbottomley@parallels.com>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCHv2 0/3] Initial ZAC support
Date: Wed, 05 Nov 2014 16:09:20 +0100 [thread overview]
Message-ID: <545A3DA0.5060901@suse.de> (raw)
In-Reply-To: <20141105150340.GA1326@lst.de>
On 11/05/2014 04:03 PM, Christoph Hellwig wrote:
> On Wed, Nov 05, 2014 at 01:08:19PM +0100, Hannes Reinecke wrote:
>> Hi all,
>>
>> this patchset updates the ATA stack to correctly detect
>> host-managed ZAC devices.
>
> And more importantly exports /dev/sg nodes from them so they can be
> actually be accessed.
>
> I'm fine with taking the whole series through the libata tree, so far
> there are no conflicting libsas changes on the radar.
>
Tejun?
I've made the requested changes of using taskfiles in libsas,
so everything should be fine now ...
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 21284 (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
next prev parent reply other threads:[~2014-11-05 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 12:08 [PATCHv2 0/3] Initial ZAC support Hannes Reinecke
2014-11-05 12:08 ` [PATCH 1/3] libsas: use ata_dev_classify() Hannes Reinecke
2014-11-05 12:08 ` [PATCH 2/3] libata: Implement ATA_DEV_ZAC Hannes Reinecke
2014-11-05 12:08 ` [PATCH 3/3] libata-scsi: Update SATL for ZAC drives Hannes Reinecke
2014-11-05 15:03 ` [PATCHv2 0/3] Initial ZAC support Christoph Hellwig
2014-11-05 15:09 ` Hannes Reinecke [this message]
2014-11-05 16:22 ` Tejun Heo
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=545A3DA0.5060901@suse.de \
--to=hare@suse.de \
--cc=hch@lst.de \
--cc=jbottomley@parallels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tj@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).