public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Phil Carmody <ext-phil.2.carmody@nokia.com>
Cc: "dedekind1@gmail.com" <dedekind1@gmail.com>,
	Takashi Iwai <tiwai@suse.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Sitsofe Wheeler <sitsofe@yahoo.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Christof Schmitt <christof.schmitt@de.ibm.com>
Subject: Re: [PULL] param sysfs oops (simple, leaky) fix, bool arrays fix
Date: Wed, 23 Jun 2010 08:53:58 +0930	[thread overview]
Message-ID: <201006230854.00441.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20100622165011.GZ17639@pcarmody-desktop>

On Wed, 23 Jun 2010 02:20:11 am Phil Carmody wrote:
> Artem's passed the baton over to me to investigate, so I've reviewed
> and back-ported the last known version of your patchset. I'm happy to 
> report that the 100% reproducable leak that we were seeing before
> cannot be reproduced. As expected, given review of the code. I have 
> not been able to test the final driver-specific patches from your 
> patchset, but up to and including
> 
> [PATCH 12/18] param: simple locking for sysfs-writable charp parameters
> 
> they can all have a:
> 
> Tested-by: Phil Carmody <ext-phil.2.carmody@nokia.com>
> 
> I'm quite interested to see these pushed into the mainline so that I
> can cherry-pick final versions for our internal tree, do you have any 
> schedule for that?

Thanks, Phil, I've added that.  Testing is always good!

The patches are sitting in linux-next now, ready for the next merge window
(ie. 2.6.36)

Cheers,
Rusty.

      reply	other threads:[~2010-06-22 23:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28 22:32 [PULL] param sysfs oops (simple, leaky) fix, bool arrays fix Rusty Russell
2010-04-27 10:31 ` Artem Bityutskiy
2010-04-27 10:53   ` Artem Bityutskiy
2010-05-04  2:23     ` Rusty Russell
2010-05-04 18:07       ` Artem Bityutskiy
2010-05-05  5:33         ` Rusty Russell
2010-05-05  7:25           ` Artem Bityutskiy
2010-05-05  7:44             ` Takashi Iwai
2010-05-05  8:49               ` Artem Bityutskiy
2010-05-05  9:04                 ` Artem Bityutskiy
2010-05-06  6:24                   ` Takashi Iwai
2010-05-06  2:28                 ` Rusty Russell
2010-06-22 16:50                   ` Phil Carmody
2010-06-22 23:23                     ` Rusty Russell [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=201006230854.00441.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=christof.schmitt@de.ibm.com \
    --cc=dedekind1@gmail.com \
    --cc=ext-phil.2.carmody@nokia.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sitsofe@yahoo.com \
    --cc=tiwai@suse.de \
    --cc=torvalds@linux-foundation.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