public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Kuan Luo <kluo@nvidia.com>
Cc: Allen Martin <AMartin@nvidia.com>, Tejun Heo <htejun@gmail.com>,
	Mark Lord <liml@rtr.ca>, Jeff Garzik <jeff@garzik.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Peer Chen <pchen@nvidia.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	David Milburn <dmilburn@redhat.com>
Subject: Re: fixed a bug of adma in rhel4u5 with HDS7250SASUN500G.
Date: Mon, 28 Jan 2008 17:50:56 -0600	[thread overview]
Message-ID: <479E6A60.5070208@shaw.ca> (raw)
In-Reply-To: <15F501D1A78BD343BE8F4D8DB854566B1BFE2ACA@hkemmail01.nvidia.com>

Kuan Luo wrote:
> Robert worte.
>> Kuan, does this patch (using the notifiers to see if the command is 
>> really done) still work if one port on the controller has 
>> ADMA disabled 
>> because it's in ATAPI mode? I seem to recall Allen Martin mentioning 
>> that notifiers wouldn't work in this case.
>>
> 
> I just tried the 2.6.24-rc7 sata_nv driver with one hd and  one cdrom in
> the same controller. 
> I mkfs hd and mounted the cdrom and no error happened.
> 
> Allen,  is there anything about notifier that we should pay attention
> to?

Assuming not, then this patch should be applied..


  reply	other threads:[~2008-01-28 23:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4781F008.9070404@gmail.com>
     [not found] ` <4782422C.8020202@rtr.ca>
     [not found]   ` <4782B73B.8080309@shaw.ca>
     [not found]     ` <4782BC48.4000309@gmail.com>
     [not found]       ` <4782C008.3030902@shaw.ca>
     [not found]         ` <4782CB62.7040901@gmail.com>
     [not found]           ` <4782CEF9.3040708@gmail.com>
     [not found]             ` <4782DFFE.50301@shaw.ca>
     [not found]               ` <4782E5A8.9010305@gmail.com>
     [not found]                 ` <4782E63E.1000606@gmail.com>
     [not found]                   ` <4782E78F.9050205@shaw.ca>
     [not found]                     ` <4782E912.1050204@gmail.com>
     [not found]                       ` <4783493A.7070800@gmail.com>
     [not found]                         ` <47838B57.8020407@shaw.ca>
     [not found]                           ` <47842A54.2060107@gmail.com>
     [not found]                             ` <47842ABA.2060605@gmail.com>
     [not found]                               ` <47844471.4070705@shaw.ca>
     [not found]                                 ` <47845708.6060900@gmail.com>
     [not found]                                   ` <478567D8.10601@shaw.ca>
     [not found]                                     ` <15F501D1A78BD343BE8F4D8DB854566B1BFE2ABF@hkemmail01.nvidia.com>
2008-01-12  1:07                                       ` fixed a bug of adma in rhel4u5 with HDS7250SASUN500G Robert Hancock
2008-01-14  3:08                                         ` Kuan Luo
2008-01-14  5:20                                           ` Robert Hancock
2008-01-14  6:23                                             ` Kuan Luo
2008-01-23  9:32                                             ` sata_nv and 2.6.24 (was Re: fixed a bug of adma in rhel4u5 with HDS7250SASUN500G.) Jeff Garzik
2008-01-23 14:44                                               ` Robert Hancock
2008-01-24  1:42                                                 ` Jeff Garzik
2008-01-24  1:53                                                   ` Robert Hancock
2008-01-24  0:43                                           ` fixed a bug of adma in rhel4u5 with HDS7250SASUN500G Robert Hancock
2008-01-24  3:20                                             ` Kuan Luo
2008-01-28 23:50                                               ` Robert Hancock [this message]
2008-01-29  2:48                                                 ` Kuan Luo
2008-01-29  4:59                                                 ` Kuan Luo

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=479E6A60.5070208@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=AMartin@nvidia.com \
    --cc=dmilburn@redhat.com \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=kluo@nvidia.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pchen@nvidia.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