From: Greg KH <greg@kroah.com>
To: "Zhao, Yu" <yu.zhao@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for March 7: slab corruptions
Date: Wed, 4 Feb 2009 21:38:02 -0800 [thread overview]
Message-ID: <20090205053802.GA8355@kroah.com> (raw)
In-Reply-To: <498A7463.4010603@intel.com>
On Thu, Feb 05, 2009 at 01:08:51PM +0800, Zhao, Yu wrote:
> Hi Greg,
>
> It looks like following fix is not in Linus' tree. Can you please queue it?
>
> http://lkml.org/lkml/2008/3/8/155
Queue what? That is a message from over a year ago, are you seeing a
problem in mainline in this area? If so, do you have a proposed fix for
it?
totally confused,
greg k-h
next prev parent reply other threads:[~2009-02-05 5:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 5:08 linux-next: Tree for March 7: slab corruptions Zhao, Yu
2009-02-05 5:38 ` Greg KH [this message]
2009-02-05 7:27 ` Zhao, Yu
2009-02-05 15:26 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2008-03-07 3:18 linux-next: Tree for March 7 Stephen Rothwell
2008-03-08 10:45 ` linux-next: Tree for March 7: slab corruptions Laurent Riffard
2008-03-08 18:59 ` Balaji Rao
2008-03-09 3:05 ` Greg KH
2008-03-09 8:13 ` Laurent Riffard
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=20090205053802.GA8355@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yu.zhao@intel.com \
/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