From: Andrew Morton <akpm@linux-foundation.org>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
linux-stable <stable@kernel.org>, Adrian Bunk <bunk@stusta.de>
Subject: Re: Three critical patches still aren't merged in 2.6.21
Date: Thu, 15 Mar 2007 11:25:32 -0800 [thread overview]
Message-ID: <20070315112532.7d6a6521.akpm@linux-foundation.org> (raw)
In-Reply-To: <45F9757F.2020900@redhat.com>
On Thu, 15 Mar 2007 12:34:07 -0400 Chuck Ebbert <cebbert@redhat.com> wrote:
> I've been holding off sending these in for -stable until they're
> merged, but now I wonder when that will happen.
We'll get there. I just got off the plane.
> http://lkml.org/lkml/2007/3/14/99
> [PATCH] hrtimer: prevent overrun DoS in hrtimer_forward()
> From: Thomas Gleixner <tglx@linutronix,de>
>
> http://lkml.org/lkml/2007/3/12/268
> NFS: nfs_getattr() can't call nfs_sync_mapping_range() for non-regular files
> From: Trond Myklebust <Trond.Myklebust@netapp.com>
>
> http://lkml.org/lkml/2007/3/12/60
> [patch] futex: PI state locking fix
> From: Ingo Molnar <mingo@elte.hu>
I have all three in various stages of queuedness, but I am presently
expecting Trond to merge the NFS one. I can send it if he wants?
next prev parent reply other threads:[~2007-03-15 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 16:34 Three critical patches still aren't merged in 2.6.21 Chuck Ebbert
2007-03-15 19:25 ` Andrew Morton [this message]
2007-03-15 19:29 ` Trond Myklebust
2007-03-16 2:12 ` [stable] " Greg KH
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=20070315112532.7d6a6521.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=trond.myklebust@fys.uio.no \
/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