All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tejun Heo <tj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] char_dev: add cdev->release() and convert cdev_alloc() to use it
Date: Thu, 28 Aug 2008 09:47:41 -0700	[thread overview]
Message-ID: <20080828164741.GA17475@kroah.com> (raw)
In-Reply-To: <48B6D428.2020308@kernel.org>

On Thu, Aug 28, 2008 at 06:36:56PM +0200, Tejun Heo wrote:
> Add cdev->release() so that cdev can be considered in more involved
> object lifetime management.  cdev_alloc() used a separate ktype for
> auto-free release().  This patch converts it to use cdev->release() so
> that there's no need for separate ktype and cdev_init() can be used
> for auto-free variant too.
> 
> Signed-off-by: Tejun Heo <tj@kernel.org>

Ick, I really don't want struct cdev to be used for lifecycle
management, as it is only for major:minor stuff.  Why do you want to
make this change?

thanks,

greg k-h

  reply	other threads:[~2008-08-28 16:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28 16:36 [PATCH RESEND] char_dev: add cdev->release() and convert cdev_alloc() to use it Tejun Heo
2008-08-28 16:47 ` Greg KH [this message]
2008-08-28 16:56   ` Tejun Heo
2008-08-28 17:38     ` Greg KH
2008-08-28 17:44       ` Tejun Heo
2008-08-28 17:48         ` Greg KH
2008-08-28 17:55           ` Tejun Heo
2008-08-28 18:17             ` Greg KH
2008-11-13  8:58               ` Tejun Heo
     [not found]                 ` <492136F5.8010903@kernel.org>
     [not found]                   ` <20081117171717.GB31306@kroah.com>
     [not found]                     ` <49221CE8.1050402@kernel.org>
2008-11-18  1:40                       ` Tejun Heo
2008-11-18 13:44                         ` Boaz Harrosh
2008-11-18 15:58                           ` Tejun Heo
2008-11-19 17:59                             ` Miklos Szeredi
2008-11-20  5:54                             ` Greg KH
2008-11-20  6:28                               ` Tejun Heo
2008-11-20 11:45                                 ` Tejun Heo

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=20080828164741.GA17475@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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.