public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Liyu <raise.sail@gmail.com>
To: Dmitry Torokhov <dtor@insightbb.com>
Cc: Anssi Hannula <anssi.hannula@gmail.com>, greg <greg@kroah.com>,
	Randy Dunlap <rdunlap@xenotime.net>,
	LKML <linux-kernel@vger.kernel.org>,
	"raise.sail@gmail.com" <raise.sail@gmail.com>,
	linux-usb-devel <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] [PATCH] usb/hid: The HID Simple Driver	Interface 0.3.2 (core)
Date: Tue, 10 Oct 2006 15:08:47 +0800	[thread overview]
Message-ID: <452B46FF.90900@gmail.com> (raw)
In-Reply-To: <200610100115.41449.dtor@insightbb.com>

Hi.

    In hid-input, It seem we only call input_allocate_device(), but not
call input_free_device() at anywhere. Is there a memory leak here? Even,
I can not found this invoke in drivers/usb/hid*.c.

    Moreover, I found many usb input device driver do not call
input_free_device() at all, except when it failed to init itself.
   
    Are these purposely?

-Liyu




      reply	other threads:[~2006-10-10  7:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29  8:24 [PATCH] usb/hid: The HID Simple Driver Interface 0.3.2 (core) raise.sail
2006-09-29 16:59 ` Randy Dunlap
2006-09-29 17:35   ` Dmitry Torokhov
2006-10-08  3:07     ` raise.sail
2006-10-08 12:41       ` [linux-usb-devel] " Zephaniah E. Hull
2006-10-08 14:09         ` Dmitry Torokhov
2006-10-09  3:28           ` Liyu
2006-10-09  3:28           ` Liyu
2006-10-08 18:51       ` Anssi Hannula
2006-10-09  3:35         ` Liyu
2006-10-09 22:52           ` Anssi Hannula
2006-10-09  3:42         ` Dmitry Torokhov
2006-10-09 22:53           ` Anssi Hannula
2006-10-10  5:15             ` Dmitry Torokhov
2006-10-10  7:08               ` Liyu [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=452B46FF.90900@gmail.com \
    --to=raise.sail@gmail.com \
    --cc=anssi.hannula@gmail.com \
    --cc=dtor@insightbb.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=rdunlap@xenotime.net \
    /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