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, Yves-Alexis Perez <corsac@debian.org>,
Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCH] libsas: Disable asynchronous aborts for SATA devices
Date: Wed, 10 Jan 2018 09:15:14 +0100 [thread overview]
Message-ID: <20180110081514.GA9810@lst.de> (raw)
In-Reply-To: <1515512632-115483-1-git-send-email-hare@suse.de>
Looks fine to me for 4.15 and -stable:
Reviewed-by: Christoph Hellwig <hch@lst.de>
But we really need to fix this properly in the long run.
next prev parent reply other threads:[~2018-01-10 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 15:43 [PATCH] libsas: Disable asynchronous aborts for SATA devices Hannes Reinecke
2018-01-10 8:15 ` Christoph Hellwig [this message]
2018-01-10 8:51 ` Hannes Reinecke
2018-01-10 8:27 ` Yves-Alexis Perez
2018-01-10 21:40 ` Martin K. Petersen
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=20180110081514.GA9810@lst.de \
--to=hch@lst.de \
--cc=corsac@debian.org \
--cc=hare@suse.com \
--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