From: Jiri Slaby <jirislaby@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: one more tty reference leak [Was: 2.6.30 -mm merge plans]
Date: Tue, 24 Mar 2009 22:48:27 +0100 [thread overview]
Message-ID: <49C9552B.1090701@gmail.com> (raw)
In-Reply-To: <20090323224615.cd29edfd.akpm@linux-foundation.org>
On 24.3.2009 06:46, Andrew Morton wrote:
> isicom-isicom-kref-leak-fix.patch
> isicom-isicom-kref-leak-fix-fix.patch
...
> Merge, backport to 2.6.29.x
Could you (or Alan) also pick
http://lkml.org/lkml/2009/3/16/159
up and merge?
next prev parent reply other threads:[~2009-03-24 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 5:46 2.6.30 -mm merge plans Andrew Morton
2009-03-24 7:57 ` [BUGFIX][PATCH(resend) mmotm] memcg: try_get_mem_cgroup_from_swapcache fix (Re: 2.6.30 -mm merge plans) Daisuke Nishimura
2009-03-24 21:48 ` Jiri Slaby [this message]
2009-03-24 22:01 ` one more tty reference leak [Was: 2.6.30 -mm merge plans] Jiri Slaby
2009-03-25 1:26 ` sd-async-shutdown.patch [was: " Robert Hancock
2009-03-25 1:29 ` Shaohua Li
2009-03-25 16:24 ` 2.6.30 -mm merge plans Kumar Gala
2009-03-25 17:14 ` Coly Li
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=49C9552B.1090701@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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