All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Brian J King <bjking1@us.ibm.com>,
	"James E.J. Bottomley" <JBottomley@parallels.com>,
	linux-scsi@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] scsi/ibmvscsi: add module alias for ibmvscsic
Date: Mon, 30 Jul 2012 21:06:06 +0200	[thread overview]
Message-ID: <20120730190606.GD3155@aepfle.de> (raw)
In-Reply-To: <1343611946.21647.23.camel@pasglop>

On Mon, Jul 30, Benjamin Herrenschmidt wrote:

> On Wed, 2012-07-18 at 18:49 +0200, olaf@aepfle.de wrote:
> > From: Olaf Hering <olaf@aepfle.de>
> > 
> > The driver is named ibmvscsic, at runtime it its name is advertised as
> > ibmvscsi. For this reason mkinitrd wont pickup the driver properly.
> > Reported by IBM during SLES11 beta testing:
> > 
> > https://bugzilla.novell.com/show_bug.cgi?id=459933
> > LTC50724
> 
> So while this would work, I do wonder however whether we could instead
> fix it by simplifying the whole thing as follow since iSeries is now
> gone and so we don't need split backends anymore:
> 
> scsi/ibmvscsi: Remove backend abstraction

I cant that these things myself anymore.

Olaf

WARNING: multiple messages have this Message-ID (diff)
From: Olaf Hering <olaf@aepfle.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Brian J King <bjking1@us.ibm.com>,
	"James E.J. Bottomley" <JBottomley@parallels.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi/ibmvscsi: add module alias for ibmvscsic
Date: Mon, 30 Jul 2012 21:06:06 +0200	[thread overview]
Message-ID: <20120730190606.GD3155@aepfle.de> (raw)
In-Reply-To: <1343611946.21647.23.camel@pasglop>

On Mon, Jul 30, Benjamin Herrenschmidt wrote:

> On Wed, 2012-07-18 at 18:49 +0200, olaf@aepfle.de wrote:
> > From: Olaf Hering <olaf@aepfle.de>
> > 
> > The driver is named ibmvscsic, at runtime it its name is advertised as
> > ibmvscsi. For this reason mkinitrd wont pickup the driver properly.
> > Reported by IBM during SLES11 beta testing:
> > 
> > https://bugzilla.novell.com/show_bug.cgi?id=459933
> > LTC50724
> 
> So while this would work, I do wonder however whether we could instead
> fix it by simplifying the whole thing as follow since iSeries is now
> gone and so we don't need split backends anymore:
> 
> scsi/ibmvscsi: Remove backend abstraction

I cant that these things myself anymore.

Olaf

  reply	other threads:[~2012-07-30 19:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18 16:49 [PATCH] scsi/ibmvscsi: add module alias for ibmvscsic olaf
2012-07-18 16:49 ` olaf
2012-07-30  1:32 ` Benjamin Herrenschmidt
2012-07-30  1:32   ` Benjamin Herrenschmidt
2012-07-30 19:06   ` Olaf Hering [this message]
2012-07-30 19:06     ` Olaf Hering
2012-07-31  3:08     ` Benjamin Herrenschmidt
2012-07-31  3:08       ` Benjamin Herrenschmidt
2012-07-31 16:20       ` Brian King
2012-07-31 17:54         ` Robert Jennings
2012-07-31 17:54           ` Robert Jennings
2012-07-31 17:57         ` Robert Jennings
2012-07-31 17:57           ` Robert Jennings
2012-09-07 16:16   ` Robert Jennings
2012-09-07 16:16     ` Robert Jennings

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=20120730190606.GD3155@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=JBottomley@parallels.com \
    --cc=benh@kernel.crashing.org \
    --cc=bjking1@us.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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.