public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: scameron@beardog.cce.hp.com
Cc: stephenmcameron@gmail.com, akpm@linux-foundation.org,
	gregkh@suse.de, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: Document generic scsi device attributes
Date: Wed, 17 Aug 2011 13:35:06 -0700	[thread overview]
Message-ID: <1313613307.6345.8.camel@mulgrave> (raw)
In-Reply-To: <20110817200028.GB8422@beardog.cce.hp.com>

On Wed, 2011-08-17 at 15:00 -0500, scameron@beardog.cce.hp.com wrote:
> On Wed, Aug 17, 2011 at 12:45:06PM -0700, James Bottomley wrote:
> > On Wed, 2011-08-17 at 13:20 -0500, Stephen M. Cameron wrote:
> > > From: Stephen M. Cameron <scameron@beardog.cce.hp.com>
> > > 
> > > Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com>
> > > ---
> > >  Documentation/ABI/testing/sysfs-class-scsi_devices |  123 ++++++++++++++++++++
> > >  1 files changed, 123 insertions(+), 0 deletions(-)
> > >  create mode 100644 Documentation/ABI/testing/sysfs-class-scsi_devices
> > > 
> > > diff --git a/Documentation/ABI/testing/sysfs-class-scsi_devices b/Documentation/ABI/testing/sysfs-class-scsi_devices
> > > new file mode 100644
> > > index 0000000..ad2d36b
> > > --- /dev/null
> > > +++ b/Documentation/ABI/testing/sysfs-class-scsi_devices
> > > @@ -0,0 +1,123 @@
> > > +What:           /sys/class/scsi_device/..../device/device_blocked
> > > +Date:           December, 2002
> > > +KernelVersion:  Unknown
> > > +Contact:        James Bottomley <James.Bottomley@HansenPartnership.com>
> > 
> > Hmm, so I get fingered for every screw up in our sysfs ABI? nice wide
> > receiver buck pass move.
> 
> Uh, sorry if that wasn't the right thing to do, which it sounds
> like it wasn't.  I just put your name there because you're the SCSI
> maintainer.  I can dig through all the commits and see who added what
> if that's preferable.  Or leave the names out?  or something else?

No, don't worry, the patch is the right thing to do ... I was just
slightly amused to see my name down for all of it.

James



  reply	other threads:[~2011-08-17 20:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-17 18:20 [PATCH] scsi: Document generic scsi device attributes Stephen M. Cameron
2011-08-17 19:45 ` James Bottomley
2011-08-17 20:00   ` scameron
2011-08-17 20:35     ` James Bottomley [this message]
2011-08-18 12:47       ` Stefan Richter
2011-08-18 12:58 ` Stefan Richter
  -- strict thread matches above, loose matches on Subject: below --
2011-08-19 14:44 Stephen M. Cameron
2011-08-19 15:21 ` Douglas Gilbert
2011-08-19 15:41   ` scameron
2011-08-21 16:22     ` Stefan Richter

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=1313613307.6345.8.camel@mulgrave \
    --to=james.bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=scameron@beardog.cce.hp.com \
    --cc=stephenmcameron@gmail.com \
    /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