2.6.23-stable review patch. If anyone has any objections, please let us
know.
--
From: Christian Borntraeger <[EMAIL PROTECTED]>
commit 5d0360ee96a5ef953dbea45873c2a8c87e77d59b upstream.
We have seen ramdisk based install systems, where some pages of mapped
libraries and program
2.6.22-stable review patch. If anyone has any objections, please let us
know.
--
From: Christian Borntraeger <[EMAIL PROTECTED]>
commit 5d0360ee96a5ef953dbea45873c2a8c87e77d59b upstream.
We have seen ramdisk based install systems, where some pages of mapped
libraries and progra
On Mon, Nov 05, 2007 at 10:13:32AM -0800, Greg Kroah-Hartman wrote:
> For the last release, I stated that I thought the 2.6.22.12 release
> would be the last one in the 2.6.22.y series. Since then, I've received
> a number of other patches that would be nice to have in the .22.y tree.
>
> So, for
Am Dienstag, 6. November 2007 schrieb Jan Kara:
> In that case you might be interested in picking up the attached fix :)
> I don't know if you already didn't get it...
---
[PATCH] rd: fix data corruption on memory pressure
---
The patch is currently in mm but not yet upstream. As soon as it is
> For the last release, I stated that I thought the 2.6.22.12 release
> would be the last one in the 2.6.22.y series. Since then, I've received
> a number of other patches that would be nice to have in the .22.y tree.
>
> So, for a while, I'll keep the 2.6.22.y tree open, doing new releases
> eve
For the last release, I stated that I thought the 2.6.22.12 release
would be the last one in the 2.6.22.y series. Since then, I've received
a number of other patches that would be nice to have in the .22.y tree.
So, for a while, I'll keep the 2.6.22.y tree open, doing new releases
every once in a
6 matches
Mail list logo
