All of lore.kernel.org
 help / color / mirror / Atom feed
From: <gregkh@suse.de>
To: kay.sievers@vrfy.org, gregkh@suse.de, greg@kroah.com,
	linux-kernel@vger.kernel.org
Subject: patch driver-core-devtmpfs-cleanup-node-on-device-creation-error.patch added to gregkh-2.6 tree
Date: Thu, 29 Oct 2009 12:29:05 -0700	[thread overview]
Message-ID: <12568445451759@kroah.org> (raw)
In-Reply-To: <1256755897.2618.324.camel@yio.site>


This is a note to let you know that I've just added the patch titled

    Subject: Driver Core: devtmpfs: cleanup node on device creation error

to my gregkh-2.6 tree.  Its filename is

    driver-core-devtmpfs-cleanup-node-on-device-creation-error.patch

This tree can be found at 
    http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/


>From kay.sievers@vrfy.org  Thu Oct 29 12:01:25 2009
From: Kay Sievers <kay.sievers@vrfy.org>
Date: Wed, 28 Oct 2009 19:51:37 +0100
Subject: Driver Core: devtmpfs: cleanup node on device creation error
To: Greg KH <greg@kroah.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Message-ID: <1256755897.2618.324.camel@yio.site>


From: Kay Sievers <kay.sievers@vrfy.org>

Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

---
 drivers/base/core.c |    2 ++
 1 file changed, 2 insertions(+)

--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -987,6 +987,8 @@ done:
 	device_remove_class_symlinks(dev);
  SymlinkError:
 	if (MAJOR(dev->devt))
+		devtmpfs_delete_node(dev);
+	if (MAJOR(dev->devt))
 		device_remove_sys_dev_entry(dev);
  devtattrError:
 	if (MAJOR(dev->devt))


      reply	other threads:[~2009-10-29 19:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28 18:51 Driver-Core: devtmpfs - cleanup node on device creation error Kay Sievers
2009-10-29 19:29 ` gregkh [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=12568445451759@kroah.org \
    --to=gregkh@suse.de \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.