From: Christoph Hellwig <hch@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Christoph Hellwig <hsh@infradead.org>,
James Bottomley <jbottomley@parallels.com>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH 4/4] sd: Optionally attach to ZBC devices
Date: Wed, 30 Jul 2014 04:39:05 -0700 [thread overview]
Message-ID: <20140730113905.GA12037@infradead.org> (raw)
In-Reply-To: <53D893B3.6020407@suse.de>
On Wed, Jul 30, 2014 at 08:41:55AM +0200, Hannes Reinecke wrote:
> Yes, eventually. But can't we defer that to a next patchset?
> I'd really like to have this one in, as it makes dealing with ZAC devices
> _so much_ easier ...
I'm happy to put the sd patch in if I can get another review for it.
But even if you want me to carry the libata bits I will need a clear
ACK from Tejun. And I really think it would belong into the libata
tree.
next prev parent reply other threads:[~2014-07-30 11:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 14:45 [PATCHv3 0/4] Initial SMR drive support Hannes Reinecke
2014-07-29 14:45 ` [PATCH 1/4] libata: consolidate ata_dev_classify() Hannes Reinecke
2014-07-29 14:45 ` [PATCH 2/4] libata: Implement ATA_DEV_ZAC Hannes Reinecke
2014-07-29 14:45 ` [PATCH 3/4] libata-scsi: Update SATL for ZAC drives Hannes Reinecke
2014-07-29 17:12 ` Christoph Hellwig
2014-07-30 6:18 ` Hannes Reinecke
2014-07-29 14:45 ` [PATCH 4/4] sd: Optionally attach to ZBC devices Hannes Reinecke
2014-07-29 17:14 ` Christoph Hellwig
2014-07-30 6:41 ` Hannes Reinecke
2014-07-30 11:39 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-30 7:55 [PATCHv4 0/4] Initial SMR drive support Hannes Reinecke
2014-07-30 7:55 ` [PATCH 4/4] sd: Optionally attach to ZBC devices 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=20140730113905.GA12037@infradead.org \
--to=hch@infradead.org \
--cc=hare@suse.de \
--cc=hsh@infradead.org \
--cc=jbottomley@parallels.com \
--cc=linux-ide@vger.kernel.org \
--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).