linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: linux-scsi@vger.kernel.org, JBottomley@parallels.com,
	xen-devel@lists.xen.org, hch@infradead.org,
	target-devel@vger.kernel.org, david.vrabel@citrix.com
Subject: Re: [Xen-devel] [PATCH V3 1/4] Add XEN pvSCSI protocol description
Date: Mon, 04 Aug 2014 12:39:58 +0200	[thread overview]
Message-ID: <53DF62FE.7030007@suse.com> (raw)
In-Reply-To: <53DF78290200007800028E39@mail.emea.novell.com>

On 08/04/2014 12:10 PM, Jan Beulich wrote:
>>>> On 04.08.14 at 10:27, <JGross@suse.com> wrote:
>> +/* Requests from the frontend to the backend */
>> +
>> +/*
>> + * Request a SCSI operation specified via a CDB in vscsiif_request.cmnd.
>> + * The target is specified via channel, id and lun.
>> + */
>> +#define VSCSIIF_ACT_SCSI_CDB		1
>> +
>> +/*
>> + * Request abort of a running operation for the specified target given by
>> + * channel, id, lun and the operation's rqid in ref_rqid.
>> + */
>> +#define VSCSIIF_ACT_SCSI_ABORT		2
>> +
>> +/*
>> + * Request a device reset of the specified target (channel and id).
>> + */
>> +#define VSCSIIF_ACT_SCSI_RESET		3
>
> While I realize you don't want to support it, leaving out
> VSCSIIF_ACT_SCSI_SG_PRESET altogether from this header may
> lead people to the false impression that its number is available for
> other use. I would generally recommend the Linux headers to not
> deviate from the master ones more than absolutely necessary,
> keeping what isn't needed/wanted by Linux at least in commented
> out form.

Okay. I'll re-add the #define


Juergen

  reply	other threads:[~2014-08-04 10:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-04  8:27 [PATCH V3 0/4] Add XEN pvSCSI support jgross
2014-08-04  8:27 ` [PATCH V3 1/4] Add XEN pvSCSI protocol description jgross
2014-08-04 10:10   ` [Xen-devel] " Jan Beulich
2014-08-04 10:39     ` Juergen Gross [this message]
2014-08-04  8:27 ` [PATCH V3 2/4] Introduce xen-scsifront module jgross
2014-08-04 12:16   ` David Vrabel
2014-08-04  8:27 ` [PATCH V3 3/4] Introduce XEN scsiback module jgross
2014-08-04 12:18   ` David Vrabel
2014-08-04  8:27 ` [PATCH V3 4/4] add xen pvscsi maintainer jgross

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=53DF62FE.7030007@suse.com \
    --to=jgross@suse.com \
    --cc=JBeulich@suse.com \
    --cc=JBottomley@parallels.com \
    --cc=david.vrabel@citrix.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=target-devel@vger.kernel.org \
    --cc=xen-devel@lists.xen.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).