All of lore.kernel.org
 help / color / mirror / Atom feed
From: ravianand <ravi.anand@qlogic.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: David Howells <dhowells@redhat.com>,
	linux-driver@qlogic.com, linux-scsi@vger.kernel.org
Subject: Re: Symbol conflict in QLA drivers
Date: Thu, 5 Oct 2006 13:14:07 -0700	[thread overview]
Message-ID: <20061005201407.GA7925@ranandlinuxbox.oc.cox.net> (raw)
In-Reply-To: <1160064812.17994.30.camel@mulgrave.il.steeleye.com>

>On Thu, 05 Oct 2006, James Bottomley wrote:
> On Thu, 2006-10-05 at 07:27 -0700, ravianand wrote:
> > We will push a patch to fix it in qla4xxx driver.
> 
> Actually, if the symbol can't be made static, please fix both (say with
> a qla2/qla4 prefix or something) just so we don't get clashes with other
> areas of the kernel.
> 

Make sense. We will fix both.

Thanx
Ravi

      reply	other threads:[~2006-10-05 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 13:41 Symbol conflict in QLA drivers David Howells
2006-10-05 14:27 ` ravianand
2006-10-05 16:13   ` James Bottomley
2006-10-05 20:14     ` ravianand [this message]

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=20061005201407.GA7925@ranandlinuxbox.oc.cox.net \
    --to=ravi.anand@qlogic.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=dhowells@redhat.com \
    --cc=linux-driver@qlogic.com \
    --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.