linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: gettinther <gettinther@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
	lists@ku-gbr.de, linux@sun7.cn, Robert Hancock <hancockr@shaw.ca>
Subject: Re: Can you please test the attached patch for nv hardreset problem?
Date: Tue, 14 Oct 2008 10:18:32 +0900	[thread overview]
Message-ID: <48F3F368.2090901@kernel.org> (raw)
In-Reply-To: <64630f150810131213m64d8fc72j38debf71a692db16@mail.gmail.com>

gettinther wrote:
> On Mon, Oct 13, 2008 at 9:27 AM, Tejun Heo <tj@kernel.org> wrote:
>> gettinther wrote:
>>> OK, patching the 2.6.26 based on your patch doesn't work properly.  It
>>> works for sata devices but not sata emulated devices (but these do
>>> work with the 2.6.27).
>> Eh... what do you mean it doesn't work on 2.6.26?  The same change
>> doesn't work on 2.6.26 but it does on 2.6.27?  How did you apply the
>> change to 2.6.26?  Can you post the diff?
>>
>> Thanks.
>>
>> --
>> tejun
>>
> 
> Sorry, replied on the wrong thread
> 
> Here's the patch I applied

Hmm... that should work for 2.6.26 for MCP55.  Can you post the failing log?

-- 
tejun

  reply	other threads:[~2008-10-14  1:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-05  0:49 Can you please test the attached patch for nv hardreset problem? Tejun Heo
2008-10-11 23:34 ` gettinther
2008-10-13  8:27   ` Tejun Heo
2008-10-13 19:13     ` gettinther
2008-10-14  1:18       ` Tejun Heo [this message]
2008-10-14 21:31         ` gettinther
2008-10-15  5:22           ` Tejun Heo
2008-10-15 20:23             ` gettinther
2008-10-16  1:44               ` Tejun Heo
2008-10-16  7:04                 ` gettinther
2008-10-17  8:25                   ` gettinther
2008-10-21  7:02                     ` gettinther

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=48F3F368.2090901@kernel.org \
    --to=tj@kernel.org \
    --cc=gettinther@gmail.com \
    --cc=hancockr@shaw.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux@sun7.cn \
    --cc=lists@ku-gbr.de \
    /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).