From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>,
James Bottomley <james.bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/3] scsi_dh: switch to scsi_execute_req_flags()
Date: Tue, 1 Nov 2016 15:41:56 +0100 [thread overview]
Message-ID: <20161101144156.GA17827@lst.de> (raw)
In-Reply-To: <1477936770-106687-1-git-send-email-hare@suse.de>
A little warning: scsi_execute_req_flags grew a new argument in the block
tree to be able to specify the request-only flags. So any of these
patches would create a (mostly harmless) conflict in linux-next.
next prev parent reply other threads:[~2016-11-01 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 17:59 [PATCH 0/3] scsi_dh: switch to scsi_execute_req_flags() Hannes Reinecke
2016-10-31 17:59 ` [PATCH 1/3] scsi_dh_rdac: " Hannes Reinecke
2016-11-01 14:47 ` Christoph Hellwig
2016-11-01 19:22 ` Hannes Reinecke
2016-10-31 17:59 ` [PATCH 2/3] scsi_dh_emc: " Hannes Reinecke
2016-10-31 17:59 ` [PATCH 3/3] scsi_dh_hp_sw: " Hannes Reinecke
2016-11-01 14:41 ` Christoph Hellwig [this message]
2016-11-01 17:00 ` [PATCH 0/3] scsi_dh: " 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=20161101144156.GA17827@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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