public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	James Bottomley <james.bottomley@hansenpartnership.com>,
	Christoph Hellwig <hch@lst.de>,
	Bart van Assche <bart.vanassche@sandisk.com>,
	linux-scsi@vger.kernel.org, Ewan Milne <emilne@redhat.com>,
	Lawrence Obermann <loberman@redhat.com>,
	Benjamin Block <bblock@linux.vnet.ibm.com>,
	Steffen Maier <maier@linux.vnet.ibm.com>,
	Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCHv4 1/8] scsi_error: count medium access timeout only once per EH run
Date: Tue, 4 Apr 2017 16:05:49 +0200	[thread overview]
Message-ID: <20170404140549.GA23337@lst.de> (raw)
In-Reply-To: <1491314581-73795-2-git-send-email-hare@suse.de>

NAK - don't overload ->eh_action for two entirely different purposes.

  reply	other threads:[~2017-04-04 14:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 14:02 [PATCHv4 0/8] Hannes Reinecke
2017-04-04 14:02 ` [PATCHv4 1/8] scsi_error: count medium access timeout only once per EH run Hannes Reinecke
2017-04-04 14:05   ` Christoph Hellwig [this message]
2017-04-04 14:02 ` [PATCHv4 2/8] sd: Return SUCCESS in sd_eh_action() after device offline Hannes Reinecke
2017-04-04 14:02 ` [PATCHv4 3/8] scsi: always send command aborts Hannes Reinecke
2017-04-04 14:02 ` [PATCHv4 4/8] libsas: allow async aborts Hannes Reinecke
2017-04-04 14:02 ` [PATCHv4 5/8] scsi: make eh_eflags persistent Hannes Reinecke
2017-04-04 14:02 ` [PATCHv4 6/8] scsi: make scsi_eh_scmd_add() always succeed Hannes Reinecke
2017-04-04 14:03 ` [PATCHv4 7/8] scsi: make asynchronous aborts mandatory Hannes Reinecke
2017-04-04 14:03 ` [PATCHv4 8/8] scsi: inline command aborts Hannes Reinecke
2017-04-05  4:33   ` kbuild test robot

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=20170404140549.GA23337@lst.de \
    --to=hch@lst.de \
    --cc=bart.vanassche@sandisk.com \
    --cc=bblock@linux.vnet.ibm.com \
    --cc=emilne@redhat.com \
    --cc=hare@suse.com \
    --cc=hare@suse.de \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=loberman@redhat.com \
    --cc=maier@linux.vnet.ibm.com \
    --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