From: Oliver Neukum <oneukum@suse.de>
To: "Brandt, Todd E" <todd.e.brandt@intel.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Hard disk S3 resume time optimization
Date: Fri, 02 Aug 2013 19:05:05 +0200 [thread overview]
Message-ID: <1375463105.13494.0.camel@linux-fkkt.site> (raw)
In-Reply-To: <11E08D716F0541429B7042699DD5C1A1706804B6@FMSMSX103.amr.corp.intel.com>
On Fri, 2013-08-02 at 16:41 +0000, Brandt, Todd E wrote:
> Do you mean in terms of debug after a failure? I can resubmit the patch with the scsi_sense_hdr buffer still in place. I just wanted to keep the first draft simple to get the concept across.
How are errors reported?
Regards
Oliver
next prev parent reply other threads:[~2013-08-02 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 23:40 [PATCH] Hard disk S3 resume time optimization Brandt, Todd E
2013-08-02 12:42 ` Oliver Neukum
2013-08-02 16:41 ` Brandt, Todd E
2013-08-02 17:05 ` Oliver Neukum [this message]
2013-08-02 17:12 ` Brandt, Todd E
-- strict thread matches above, loose matches on Subject: below --
2013-05-16 22:29 Brandt, Todd E
2013-05-16 22:44 ` Tejun Heo
2013-05-16 22:47 ` Tejun Heo
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=1375463105.13494.0.camel@linux-fkkt.site \
--to=oneukum@suse.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=todd.e.brandt@intel.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