public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Greg KH <greg@kroah.com>, linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sysfs: add filter function to groups
Date: Mon, 29 Oct 2007 17:54:12 +0100	[thread overview]
Message-ID: <1193676852.2655.21.camel@lov.site> (raw)
In-Reply-To: <1193671019.3383.13.camel@localhost.localdomain>

On Mon, 2007-10-29 at 10:16 -0500, James Bottomley wrote:
> In the SCSI transport classes (and soon to be in the AEN event
> subsystem) we have a lot of need for a grouping that doesn't include all
> files in the group.  We basically want to show capability by which file
> is present.  A classic example of this is the SPI transport class
> connected to the 53c700 card.  It's incapable of doing all of the modern
> LVD functions, so we don't show any of those capabilities in its sysfs
> directory.  However, we have a lot of horrible logic to generate
> separate per host groupings of attributes for this.  We would be able to
> use the standard sysfs group attributes *if* there were a way of
> filtering them so that certain attributes didn't appear.

Sounds fine.
 
> This patch is a first pass at adding a filter function to the group
> attributes, just to see how the idea flies.  If everyone's OK with this,
> I think the next thing that we might do is add bitmap functions (so
> every bit in the bitmap has a name, but also might not appear) to
> groups.

Bitmaps in the attribute groups?

>  struct attribute_group {
>  	const char		*name;
> +	int			(*filter_show)(struct kobject *, int);

Are you sure that you want to return an array index here, instead of the
actual attribute? Like:
  int (*filter_show)(struct kobject *kobj, struct attribute *attr);

The names "show" and "store" are the ususal file-operation names, and we
are not filtering a "show" here, right? Maybe "create", or "export", or
something else might be a better name?

Thanks,
Kay


  reply	other threads:[~2007-10-29 16:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29 15:16 [PATCH] sysfs: add filter function to groups James Bottomley
2007-10-29 16:54 ` Kay Sievers [this message]
2007-10-29 16:57   ` James Bottomley
2007-10-29 17:18     ` Cornelia Huck
2007-10-29 17:24       ` James Bottomley
2007-10-29 17:27         ` Jeff Garzik
2007-10-29 17:29           ` James Bottomley
2007-10-30  9:00             ` Cornelia Huck
2007-10-30  8:55         ` Cornelia Huck
2007-10-29 17:27     ` Kay Sievers
2007-10-29 17:28       ` James Bottomley
2007-10-29 17:43         ` Kay Sievers
2007-10-29 17:58     ` Stefan Richter
2007-10-29 18:12       ` James Bottomley
2007-10-30 18:25       ` James Bottomley
2007-10-30 19:31         ` Stefan Richter
2007-10-30 19:47         ` Kay Sievers
2007-10-31  0:40         ` Mark M. Hoffman
2007-10-31  2:01           ` Kay Sievers
2007-10-31 11:28             ` Mark M. Hoffman
2007-10-31  3:55         ` Greg KH
2007-10-31  9:41           ` Cornelia Huck
2007-10-31  9:52             ` Stefan Richter
2007-10-31 10:20               ` Cornelia Huck
2007-10-31 10:37                 ` Stefan Richter
2007-10-31 12:19                   ` Cornelia Huck
2007-10-31 14:38           ` James Bottomley
2007-10-31 17:29             ` Greg KH
2007-11-04 14:12               ` James Bottomley
2007-11-04 19:06                 ` Greg KH

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=1193676852.2655.21.camel@lov.site \
    --to=kay.sievers@vrfy.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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