From: Cong Ding <dinggnu@gmail.com>
To: "Hans J. Koch" <hjk@hansjkoch.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] uio.c: solve memory leak
Date: Thu, 14 Feb 2013 12:43:15 +0100 [thread overview]
Message-ID: <20130214114315.GB18774@gmail.com> (raw)
In-Reply-To: <20130120210140.GA13035@local>
On Sun, Jan 20, 2013 at 10:01:41PM +0100, Hans J. Koch wrote:
> On Fri, Jan 18, 2013 at 02:00:50PM -0800, Greg Kroah-Hartman wrote:
> > On Fri, Jan 18, 2013 at 10:05:45PM +0100, Cong Ding wrote:
> > > On Tue, Dec 11, 2012 at 2:21 AM, Hans J. Koch <hjk@hansjkoch.de> wrote:
> > > > On Thu, Nov 29, 2012 at 05:40:00PM +0000, Cong Ding wrote:
> > > >> In version 1, I forgot to modify the same bug in the first loop.
> > > >>
> > > >> we have to call kobject_put() to clean up the kobject after function
> > > >> kobject_init(), kobject_add(), or kobject_uevent() is called.
> > > >>
> > > >> Signed-off-by: Cong Ding <dinggnu@gmail.com>
> > > >
> > > > Signed-off-by: "Hans J. Koch" <hjk@hansjkoch.de>
> > >
> > > Hi Greg, is this patch stil in the queue?
> >
> > Hans is queueing up UIO patches to send to me, I'm waiting for him to
> > send them as I don't have any in my trees.
>
> I'll set that up tonight or tomorrow. Sorry, I was delayed by illness
> and a lot of other work.
Hi Hans, what's this going on?
Thanks, - cong
next prev parent reply other threads:[~2013-02-14 11:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 17:40 [PATCH v2 1/1] uio.c: solve memory leak Cong Ding
2012-11-30 0:13 ` Hans J. Koch
2012-11-30 11:03 ` Cong Ding
2012-12-06 23:02 ` Cong Ding
2012-12-08 0:10 ` Hans J. Koch
2012-12-08 0:15 ` Cong Ding
2012-12-11 1:21 ` Hans J. Koch
2013-01-18 21:05 ` Cong Ding
2013-01-18 22:00 ` Greg Kroah-Hartman
2013-01-20 21:01 ` Hans J. Koch
2013-02-14 11:43 ` Cong Ding [this message]
2013-04-25 10:19 ` Cong Ding
2013-05-26 22:14 ` Cong Ding
2013-07-25 7:05 ` Cong Ding
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=20130214114315.GB18774@gmail.com \
--to=dinggnu@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox