mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: jens.axboe@oracle.com, andrew.patterson@hp.com,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	scameron@beardog.cca.cpqcorp.net
Subject: Re: [PATCH v6] cciss: add cciss driver sysfs entries
Date: Fri, 29 May 2009 16:32:18 -0500	[thread overview]
Message-ID: <20090529213218.GA20102@beardog.cca.cpqcorp.net> (raw)
In-Reply-To: <20090529124813.689b7667.akpm@linux-foundation.org>

On Fri, May 29, 2009 at 12:48:13PM -0700, Andrew Morton wrote:
> On Thu, 28 May 2009 15:21:24 -0500
> "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net> wrote:
> 
> > From: Andrew Patterson <andrew.patterson@hp.com>
> > 
> > This patch adds sysfs entries to the cciss driver needed for the
> > dm/multipath tools. A file for vendor, model, rev, and unique_id is
> > added for each logical drive under directory
> > /sys/bus/pci/devices/<dev>/ccissX/cXdY. Where X = the controller (or
> > host) number and Y is the logical drive number. A link from
> > /sys/bus/pci/devices/<dev>/ccissX/cXdY/block:cciss!cXdY to
> > /sys/block/cciss!cXdY/device is also created. A bus is created
> > in /sys/bus/cciss.  A link is created from the pci ccissX entry to
> > /sys/bus/cciss/devices/ccissX.
> > Please consider this for inclusion.
> > 
> > Signed-off-by: Mike Miller <mike.miller@hp.com>
> 
> Did Andrew's signed-off-by: get lost?

No, I converted it into the From: field. Another screw up, I guess.

mikem

  reply	other threads:[~2009-05-29 21:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090413164524.17977.99322.stgit@bluto.andrew>
     [not found] ` <20090413164530.17977.32550.stgit@bluto.andrew>
2009-05-28 20:21   ` Mike Miller (OS Dev)
2009-05-29 19:48     ` Andrew Morton
2009-05-29 21:32       ` Mike Miller (OS Dev) [this message]
2009-05-28 20:24 ` Mike Miller (OS Dev)

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=20090529213218.GA20102@beardog.cca.cpqcorp.net \
    --to=mikem@beardog.cca.cpqcorp.net \
    --cc=akpm@linux-foundation.org \
    --cc=andrew.patterson@hp.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=scameron@beardog.cca.cpqcorp.net \
    /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®