All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: Christoph Hellwig <hch@lst.de>
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: qla1280 compile problems
Date: 05 Aug 2003 08:40:03 -0400	[thread overview]
Message-ID: <m31xw0wa58.fsf@trained-monkey.org> (raw)
In-Reply-To: <20030805121813.GA24647@lst.de>

>>>>> "Christoph" == Christoph Hellwig <hch@lst.de> writes:

Christoph> The qla1280 update still has some issues, mostly because it
Christoph> backs out all the 2.5 changes applied to the driver in the
Christoph> last months, also it doesn't work on ia64 because the IA64
Christoph> generic build references sn2-specific symbols that don't
Christoph> exist in that build.

Christoph,

Which version of the driver are you testing and what kernel? I tried
it out fairly recently on 2.5.x (2.5.59 or so) and it compiled without
any problems.

Christoph> Jes, can you look at the 2.5 changes that went in after
Christoph> your last merge and make the SN2 vchan workaround a config
Christoph> option?

I will take a look at building it against the latest 2.6.0-test
kernel. However, I am not going to make the vchan workaround a new
config option, it doesn't make any sense as it's already protected by
CONFIG_IA64_SGI_SN2 || CONFIG_IA64_GENERIC. The appropriate patches
for that have already been pushed for 2.4 and Jesse is about to push
them out for 2.5.

Cheers,
Jes

  reply	other threads:[~2003-08-05 12:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 12:18 qla1280 compile problems Christoph Hellwig
2003-08-05 12:40 ` Jes Sorensen [this message]
2003-08-05 12:49   ` Christoph Hellwig
2003-08-05 12:54     ` Jes Sorensen
2003-08-05 16:17 ` James Bottomley
2003-08-05 16:31   ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2003-08-05 12:15 Christoph Hellwig

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=m31xw0wa58.fsf@trained-monkey.org \
    --to=jes@wildopensource.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.