mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Greg KH <gregkh@suse.de>
Cc: Gabriel C <nix.or.die@googlemail.com>,
	Robert Schwebel <r.schwebel@pengutronix.de>,
	Jan Engelhardt <jengelh@computergmbh.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kay.sievers@vrfy.org
Subject: Re: kobject link failure
Date: Fri, 20 Jul 2007 11:32:21 +0200	[thread overview]
Message-ID: <20070720113221.390ed32a@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20070720080059.GA29639@suse.de>

On Fri, 20 Jul 2007 01:00:59 -0700,
Greg KH <gregkh@suse.de> wrote:


> --- a/drivers/base/core.c
> +++ b/drivers/base/core.c
> @@ -250,6 +250,7 @@ static struct kset_uevent_ops device_uev
>  	.uevent =	dev_uevent,
>  };
> 
> +#ifdef CONFIG_HOTPLUG
>  static ssize_t show_uevent(struct device *dev, struct device_attribute *attr,
>  			   char *buf)
>  {
> @@ -330,6 +331,23 @@ out:
>  static struct device_attribute uevent_attr =
>  	__ATTR(uevent, S_IRUGO | S_IWUSR, show_uevent, store_uevent);
> 
> +static int device_add_uevent_attr(struct device *dev)
> +{
> +	return device_create_file(dev, &uevent_attr);
> +}
> +
> +static void device_remove_uevent_attr(struct device *dev)
> +{
> +	device_remove_file(dev, &uevent_attr);
> +}
> +
> +#else	/* CONFIG_HOTPLUG */
> +
> +static inline int device_add_uevent_attr(struct device *dev) { return 0; }
> +static inline void device_remove_uevent_attr(struct device *dev) { }
> +
> +#endif	/* CONFIG_HOTPLUG */
> +
>  static int device_add_attributes(struct device *dev,
>  				 struct device_attribute *attrs)
>  {
> @@ -787,7 +805,7 @@ int device_add(struct device *dev)
>  		blocking_notifier_call_chain(&dev->bus->bus_notifier,
>  					     BUS_NOTIFY_ADD_DEVICE, dev);
> 
> -	error = device_create_file(dev, &uevent_attr);
> +	error = device_add_uevent_attr(dev);
>  	if (error)
>  		goto attrError;
> 
> @@ -861,7 +879,7 @@ int device_add(struct device *dev)
>  		}
>  	}
>   ueventattrError:
> -	device_remove_file(dev, &uevent_attr);
> +	device_remove_uevent_attr(dev);
>   attrError:
>  	kobject_uevent(&dev->kobj, KOBJ_REMOVE);
>  	kobject_del(&dev->kobj);
> @@ -994,7 +1012,7 @@ void device_del(struct device * dev)
>  			up(&dev->class->sem);
>  		}
>  	}
> -	device_remove_file(dev, &uevent_attr);
> +	device_remove_uevent_attr(dev);
>  	device_remove_attrs(dev);
>  	bus_remove_device(dev);
> 

Hm, this would be an interface change (the uevent attribute used to
exist even for !CONFIG_HOTPLUG, it just triggered nothing). How about
moving kobject_actions[] out of the #ifdef (maybe next to
kobject_action)?

  reply	other threads:[~2007-07-20  9:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19 18:03 Jan Engelhardt
2007-07-19 18:11 ` Gabriel C
2007-07-19 19:19   ` Greg KH
2007-07-20  8:00   ` Greg KH
2007-07-20  9:32     ` Cornelia Huck [this message]
2007-07-20 11:58       ` Cornelia Huck
2007-07-20 15:06         ` Greg KH
2007-07-20 16:02           ` Jan Engelhardt
2007-07-19 19:18 ` Greg KH
2007-07-19 20:00   ` Jan Engelhardt

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=20070720113221.390ed32a@gondolin.boeblingen.de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=gregkh@suse.de \
    --cc=jengelh@computergmbh.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix.or.die@googlemail.com \
    --cc=r.schwebel@pengutronix.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

all inboxes | Powered by JetHome®