From: Greg KH <greg@kroah.com>
To: Federico Vaga <federico.vaga@gmail.com>
Cc: Alessandro Rubini <rubini@gnudd.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
dcobas@cern.ch, siglesia@cern.ch, manohar.vanga@cern.ch
Subject: Re: [RFC PATCH 3/7] drivers/zio: core files for the ZIO input/output
Date: Sun, 27 Nov 2011 01:33:21 -0800 [thread overview]
Message-ID: <20111127093321.GC31086@kroah.com> (raw)
In-Reply-To: <7431481.TL8TOhprdN@harkonnen>
On Sat, Nov 26, 2011 at 11:58:41PM +0100, Federico Vaga wrote:
> In data sabato 26 novembre 2011 12:03:41, Greg KH ha scritto:
> > On Sat, Nov 26, 2011 at 06:30:42PM +0100, Alessandro Rubini wrote:
> > > +static struct kobj_type zdktype = { /* For standard and extended
> > > attribute */ + .release = NULL,
> >
> > Sweet!
> >
> > As-per the in-kernel documentation, I now get to mock you for doing
> > this :)
> >
> > Please NEVER DO THIS, you are ignoring the messages that the kernel
> > sends you when you remove one of these devices, and causing a memory
> > leak.
>
> Honestly we never see any messages about this.
Really? Then you never removed that kobject from memory. Please go
read the kobject documentation for more details.
> > Not nice at all, yet another reason to use a 'struct device'.
>
> I don't think is a valid reason, because device_release implementation require
> us to implement a release method within device, or device_type or class; so we
> can use kobj_type as well.
True, but it tries to make things easier to not get wrong, like you are
here.
Please fix this.
greg k-h
next prev parent reply other threads:[~2011-11-27 10:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-26 17:30 [RFC PATCH 0/7] Introducing ZIO, a new I/O framework Alessandro Rubini
2011-11-26 17:30 ` [RFC PATCH 1/7] Documentation: add docs for drivers/zio Alessandro Rubini
2011-11-26 20:00 ` Greg KH
2011-11-26 21:48 ` Federico Vaga
2011-11-26 22:16 ` Jonathan Cameron
2011-11-26 22:53 ` Alessandro Rubini
2011-12-06 5:12 ` Randy Dunlap
2011-11-26 17:30 ` [RFC PATCH 2/7] include/linux: add headers " Alessandro Rubini
2011-11-26 20:02 ` Greg KH
2011-11-26 21:46 ` Federico Vaga
2011-11-27 9:32 ` Greg KH
2011-11-28 14:56 ` Federico Vaga
2011-11-30 6:21 ` Greg KH
2011-11-26 17:30 ` [RFC PATCH 3/7] drivers/zio: core files for the ZIO input/output Alessandro Rubini
2011-11-26 20:03 ` Greg KH
2011-11-26 22:58 ` Federico Vaga
2011-11-27 9:33 ` Greg KH [this message]
2011-11-28 14:59 ` Federico Vaga
2011-11-26 17:30 ` [RFC PATCH 4/7] drivers/zio: add triggers and buffers Alessandro Rubini
2011-11-26 17:31 ` [RFC PATCH 5/7] drivers/zio: add the zio-zero device driver Alessandro Rubini
2011-11-26 17:31 ` [RFC PATCH 6/7] drivers/zio: add user-space tool zio-dump Alessandro Rubini
2011-11-26 17:31 ` [RFC PATCH 7/7] zio: insert in Kbuild so it is actually compiled Alessandro Rubini
2011-11-26 18:09 ` [RFC PATCH 0/7] Introducing ZIO, a new I/O framework Lars-Peter Clausen
2011-11-26 19:11 ` Alessandro Rubini
2011-12-01 21:41 ` Linus Walleij
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=20111127093321.GC31086@kroah.com \
--to=greg@kroah.com \
--cc=dcobas@cern.ch \
--cc=federico.vaga@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manohar.vanga@cern.ch \
--cc=rubini@gnudd.com \
--cc=siglesia@cern.ch \
/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