mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: Andi Kleen <ak@linux.intel.com>
Cc: "Ozan Çağlayan" <ozan@pardus.org.tr>,
	stable@kernel.org, giridhar.malavali@qlogic.com,
	linux-kernel@vger.kernel.org, andrew.vasquez@qlogic.com
Subject: Re: [BISECTED] QLogic Corp. ISP2532-based 8Gb Fibre Channel not working on 2.6.35.y
Date: Tue, 19 Apr 2011 12:04:08 -0500	[thread overview]
Message-ID: <1303232648.3171.22.camel@mulgrave.site> (raw)
In-Reply-To: <20110419165801.GA17788@tassilo.jf.intel.com>

On Tue, 2011-04-19 at 09:58 -0700, Andi Kleen wrote:
> > From 2f0f3f4f06f7cfadebf58b70bd9e7f71d8fd96e4 Mon Sep 17 00:00:00 2001
> > From: Madhuranath Iyengar <madhuranath.iyengar@qlogic.com>
> > Date: Fri, 23 Jul 2010 15:28:24 +0500
> > Subject: [PATCH 021/107] [SCSI] qla2xxx: Appropriately log FCP
> > priority data messages
> > 
> > Signed-off-by: Giridhar Malavali <giridhar.malavali@qlogic.com>
> > Signed-off-by: James Bottomley <James.Bottomley@suse.de>
> > 
> > 
> > -------
> > 
> > So I think at least the first commit that I've mentioned should be
> > queued for the next 2.6.35.y to fix this issue.
> 
> Thanks for the bisection.
> 
> Can I get an ack for that from the driver or SCSI maintainer or
> patch author first please?
> I don't understand the driver well enough to make a call myself.

I'll defer to qlogic ... it looks like a driver enhancement to add FCP
prioritised queues ... but it would be a bug fix, I suppose, if the card
can't actually operate without this.

James



  reply	other threads:[~2011-04-19 17:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19  9:23 Ozan Çağlayan
2011-04-19 16:58 ` Andi Kleen
2011-04-19 17:04   ` James Bottomley [this message]
2011-04-20  2:05     ` Madhu Iyengar
2011-04-20 20:57       ` Andi Kleen

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=1303232648.3171.22.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=ak@linux.intel.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=giridhar.malavali@qlogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ozan@pardus.org.tr \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®