From: Christoph Hellwig <hch@infradead.org>
To: Sergio Callegari <sergio.callegari@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>, linux-kernel@vger.kernel.org
Subject: Re: "scsi: convert host_busy to atomic_t" series causes regressions for some hardware configurations
Date: Mon, 7 Sep 2015 10:51:46 -0700 [thread overview]
Message-ID: <20150907175146.GA19989@infradead.org> (raw)
In-Reply-To: <55ED3D44.5060502@gmail.com>
Hi Sergio,
sorry for the delay. I'm fighting deadlines at the moment, so even if
this is my highest spare time priority right now I can't find enough
quiet time to dig into the problem. I'd suggest you resend a report
to linux-ide (with a Cc to linux-scsi) so that the people who know the
libata code can take look. I strongly suspect the root cause for it is
in libata anyway, which is a code base I need to get up to speed with
first.
next prev parent reply other threads:[~2015-09-07 17:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 20:58 IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition Sergio Callegari
2015-06-25 21:31 ` Borislav Petkov
2015-08-18 7:44 ` Sergio Callegari
2015-08-20 8:08 ` Christoph Hellwig
2015-08-20 15:08 ` Sergio Callegari
2015-08-24 17:07 ` "scsi: convert host_busy to atomic_t" series causes regressions for some hardware configurations Sergio Callegari
2015-08-25 11:00 ` Christoph Hellwig
2015-08-26 7:14 ` Sergio Callegari
2015-08-30 10:54 ` Sergio Callegari
2015-09-07 7:31 ` Sergio Callegari
2015-09-07 17:51 ` Christoph Hellwig [this message]
2015-07-02 16:11 ` IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition Ondrej Zary
2015-07-03 6:50 ` Sergio Callegari
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=20150907175146.GA19989@infradead.org \
--to=hch@infradead.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sergio.callegari@gmail.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;
as well as URLs for NNTP newsgroup(s).