public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Kay Sievers <kay.sievers@vrfy.org>, 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 13:12:33 -0500	[thread overview]
Message-ID: <1193681553.3383.102.camel@localhost.localdomain> (raw)
In-Reply-To: <47261F50.3050901@s5r6.in-berlin.de>

On Mon, 2007-10-29 at 18:58 +0100, Stefan Richter wrote:
> James Bottomley wrote:
> >> >  struct attribute_group {
> >> >  	const char		*name;
> >> > +	int			(*filter_show)(struct kobject *, int);
> 
> > Actually, it returns a true/false value indicating whether the given
> > attribute should be displayed.
> 
> How about this:
> 
> 	int (*is_visible)(...);
> or
> 	bool (*shall_be_shown)(...);
> or
> 	bool (*should_be_displayed)(...);
> 
> or whatever, so that it indicates that this function merely answers a
> question, but doesn't filter nor show anything.

Actually, as long as it's descriptive, I really don't care about the
name.  Can we all agree on "is_visible"?

James



  reply	other threads:[~2007-10-29 18:12 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
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 [this message]
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=1193681553.3383.102.camel@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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