public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Mark Haverkamp <markh@osdl.org>,
	Christoph Hellwig <hch@infradead.org>,
	James Bottomley <James.Bottomley@steeleye.com>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] 2.6.9 aacraid: aac_count fix
Date: Thu, 16 Sep 2004 12:29:26 +0100	[thread overview]
Message-ID: <20040916122925.A32569@infradead.org> (raw)
In-Reply-To: <60807403EABEB443939A5A7AA8A7458B1AAAB7@otce2k01.adaptec.com>; from mark_salyzyn@adaptec.com on Wed, Sep 15, 2004 at 07:47:45AM -0400

On Wed, Sep 15, 2004 at 07:47:45AM -0400, Salyzyn, Mark wrote:
> Christoph Hellwig writes:
> 
> > > +	scsi_set_device(shost, &pdev->dev);
> > 
> > This one is bogus.  scsi_add_host already sets the device.
> 
> Which path sets the device? I got an intermittent panic as a result of
> the device not being set in my unit test (of the kernel of the day at
> the time of this modification, can't remember which version of the
> kernel ...). Which version of this kernel sets it?

Since mid-2.5.x.  Maybe you try to access it before scsi_add_host is called?

  parent reply	other threads:[~2004-09-16 11:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-15 11:47 [PATCH] 2.6.9 aacraid: aac_count fix Salyzyn, Mark
2004-09-15 14:24 ` Mark Haverkamp
2004-09-16 11:29 ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-16 19:12 Salyzyn, Mark
2004-09-16 15:14 Mark Haverkamp
2004-09-16 18:22 ` Christoph Hellwig
2004-09-15 17:43 Salyzyn, Mark
2004-09-15 20:24 ` Mark Haverkamp
2004-09-14 20:12 Mark Haverkamp
2004-09-14 21:14 ` Christoph Hellwig
2004-09-14 21:37   ` Mark Haverkamp
2004-09-14 21:55     ` Christoph Hellwig
2004-09-15 14:51       ` Mark Haverkamp

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=20040916122925.A32569@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    --cc=markh@osdl.org \
    /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