linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Adaptec OEM Raid Solutions <aacraid@adaptec.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: [PATCH v2] [SCSI] dpt_i2o: use proper pci driver
Date: Wed, 17 Feb 2016 21:20:03 +0530	[thread overview]
Message-ID: <56C496AB.2070200@gmail.com> (raw)
In-Reply-To: <20160217142732.6dcad24c@lxorguk.ukuu.org.uk>

On Wednesday 17 February 2016 07:57 PM, One Thousand Gnomes wrote:
> On Wed, 17 Feb 2016 17:50:14 +0530
> Sudip Mukherjee <sudipm.mukherjee@gmail.com> wrote:
>
>> This is a pci device but was not done in the usual way a pci driver is
>> done. Convert the driver into a proper pci driver.
>
> This looks completely wrong. Please read the I2O 1.5 specification
> document before playing with that code. You can't simply convert it to a
> standard PCI driver as all the IOPs are supposed to be detected and then
> the correct initialization sequence executed across the set of IOPs. IOPs
> are allowed to talk to one another and the system table binds it all
> together.

Yes, thanks for letting me know about the spec. It is saying
"The host locates each IOP, adds it
to the system configuration table, and initializes the IOP’s outbound 
message queue. The host then
provides each IOP with a list of all IOPs and the physical location of 
their inbound message queue."

>
> If you do hot plug then you need to follow the specification and do
> all the extra notifications. Unless you've got multiple FC909/FC920
> fibechannel cards or similar to test with I would just leave this well
> alone.

point noted.

> Your original simple patch is *MUCH* safer in this specific case.

The original patch is already having NACK from Johannes. So i better 
leave this code here.

regards
sudip

  reply	other threads:[~2016-02-17 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 12:20 [PATCH v2] [SCSI] dpt_i2o: use proper pci driver Sudip Mukherjee
2016-02-17 14:27 ` One Thousand Gnomes
2016-02-17 15:50   ` Sudip Mukherjee [this message]
2016-02-18  8:19     ` Johannes Thumshirn

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=56C496AB.2070200@gmail.com \
    --to=sudipm.mukherjee@gmail.com \
    --cc=aacraid@adaptec.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=jthumshirn@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).