public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [PATCH] scsi_transport_spi: convert to attribute groups
Date: Fri, 11 Jan 2008 21:11:22 -0800	[thread overview]
Message-ID: <20080112051122.GB19894@kroah.com> (raw)
In-Reply-To: <1199549907.3399.25.camel@localhost.localdomain>

On Sat, Jan 05, 2008 at 10:18:27AM -0600, James Bottomley wrote:
> This conversion makes full use of the is_visible() callback on attribute
> groups.  Now, each device appears only with its capability flags in the
> transport class directory.  Previously each device appeared with the
> capability of the host, so this is a functionality improvement.
> Converting to attribute groups allows us to sweep away most of the home
> grown #defines that were effectively doing the same thing.
> 
> James
> 
> ---
> 
> This depends on:
> 
> [PATCH] sysfs: add filter function to groups
> [PATCH] fix the sysfs_add_file_to_group interfaces
> [PATCH] attribute_container: update to use the group interface
> [PATCH] add missing transport configure points for target and host
> 
> Greg and Kay, there's a nasty point in the code where I'd like to use
> the -EEXIST return of sysfs_add_file_to_group() to indicate the file is
> already there, however, this also dumps a stack trace and would frighten
> users ... can we get rid of the printk and the WARN_ON(1)?

I really don't want to, as it has caught a lot of problems in the past.

What do you want to do that needs this error to happen "properly"?

thanks,

greg k-h

  reply	other threads:[~2008-01-12  5:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-05 16:18 [PATCH] scsi_transport_spi: convert to attribute groups James Bottomley
2008-01-12  5:11 ` Greg KH [this message]
2008-01-12 15:34   ` James Bottomley

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=20080112051122.GB19894@kroah.com \
    --to=greg@kroah.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=kay.sievers@vrfy.org \
    --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