Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 6/10] lpfc 8.2.4 : Add additional sysfs and module parameters
Date: Fri, 11 Jan 2008 11:53:11 -0600	[thread overview]
Message-ID: <1200073991.3286.43.camel@localhost.localdomain> (raw)
In-Reply-To: <1200034389.27954.25.camel@localhost.localdomain>

On Fri, 2008-01-11 at 01:53 -0500, James Smart wrote:
> Made link speed and link topology modifiable via sysfs
> Make scatter gather Segment Count into a module parameter.
> 
> Signed-off-by: James Smart <James.Smart@emulex.com>

OK ... I put this in, but shouldn't at least the link speed and possibly
topology modifications rightly be properties of the transport class?

James



  reply	other threads:[~2008-01-11 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-11  6:53 [PATCH 6/10] lpfc 8.2.4 : Add additional sysfs and module parameters James Smart
2008-01-11 17:53 ` James Bottomley [this message]
2008-01-14 14:07   ` James Smart

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=1200073991.3286.43.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=James.Smart@Emulex.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox