public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI Hotplug fixes for 2.6.4-rc1
Date: Thu, 4 Mar 2004 10:27:34 -0800	[thread overview]
Message-ID: <20040304182734.GE13907@kroah.com> (raw)
In-Reply-To: <200403040716.51298.ioe-lkml@rameria.de>

On Thu, Mar 04, 2004 at 07:17:37AM +0100, Ingo Oeser wrote:
> Hi Greg,
> 
> On Wednesday 03 March 2004 05:21, Greg KH wrote:
> > -decl_subsys(pci_hotplug_slots, &hotplug_slot_ktype, NULL);
> > -
> > +/*
> > + * We create a struct subsystem on our own and not use decl_subsys so
> > + * we can have a sane name "slots" in sysfs, yet still keep a good
> > + * global variable name "pci_hotplug_slots_subsys.
> > + * If the decl_subsys() #define ever changes, this declaration will
> > + * need to be update to make sure everything is initialized properly.
> > + */
> > +struct subsystem pci_hotplug_slots_subsys = {
> > +	.kset = {
> > +		.kobj = { .name = "slots" },
> > +		.ktype = &hotplug_slot_ktype,
> > +	}
> > +};
> 
> How about creating a decl_subsys_name() for creating sane names,
> like we have for the module parameters?
> 
> That whould solve all those problems, since this is used not only once.

Good idea.  Care to make up such a patch?

thanks,

greg k-h

      reply	other threads:[~2004-03-04 18:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03  4:20 [BK PATCH] PCI Hotplug fixes for 2.6.4-rc1 Greg KH
2004-03-03  4:21 ` [PATCH] " Greg KH
2004-03-03  4:21   ` Greg KH
2004-03-03  4:21     ` Greg KH
2004-03-03  4:21       ` Greg KH
2004-03-03  4:21         ` Greg KH
2004-03-04  6:17     ` Ingo Oeser
2004-03-04 18:27       ` Greg KH [this message]

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=20040304182734.GE13907@kroah.com \
    --to=greg@kroah.com \
    --cc=ioe-lkml@rameria.de \
    --cc=linux-kernel@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