public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc4-mm1
Date: Sun, 31 Jul 2005 13:51:05 +0200	[thread overview]
Message-ID: <200507311351.05641.rjw@sisk.pl> (raw)
In-Reply-To: <20050731020552.72623ad4.akpm@osdl.org>

Hi,

On Sunday, 31 of July 2005 11:05, Andrew Morton wrote:
> 
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc4/2.6.13-rc4-mm1/
> 
> 
> - Dropped areca-raid-linux-scsi-driver.patch and iteraid.patch.  People who
>   need these can get them from 2.6.13-rc3-mm3.
> 
> - Dropped the CKRM patches.  I don't think they were doing much in -mm and
>   we didn't find many problems with them anyway.
> 
> - Dropped the connector patches: turns out that we no longer have a netlink
>   slot available for them anyway.

It looks like 2.6.13-rc4-mm1 is fine and dandy on two of AMD64 boxes I have
access to.  In particular, all of the problems that I've had recently with Asus L5D
seem to be gone now. :-))

I only had a problem with this kernel on a NUMA-enabled dual-Opteron box,
which hanged solid when I started to copy huge amounts of data from it over
the network.  If I'm able to reproduce it, I'll investigate it a bit more and let you
know.

Greets,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  parent reply	other threads:[~2005-07-31 11:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-31  9:05 2.6.13-rc4-mm1 Andrew Morton
2005-07-31 10:04 ` 2.6.13-rc4-mm1 Felipe Alfaro Solana
2005-07-31 10:19   ` 2.6.13-rc4-mm1 Adrian Bunk
2005-07-31 12:37     ` 2.6.13-rc4-mm1 James Courtier-Dutton
2005-07-31 12:50       ` 2.6.13-rc4-mm1 Adrian Bunk
2005-07-31 14:41   ` 2.6.13-rc4-mm1 Michael Thonke
2005-07-31 13:55     ` 2.6.13-rc4-mm1 Felipe Alfaro Solana
2005-07-31 11:51 ` Rafael J. Wysocki [this message]
2005-07-31 13:35 ` 2.6.13-rc4-mm1 Andreas Steinmetz
2005-07-31 17:47   ` 2.6.13-rc4-mm1 Andrew Morton
2005-07-31 18:49     ` 2.6.13-rc4-mm1 Andreas Steinmetz
2005-07-31 15:11 ` 2.6.13-rc4-mm1 Michael Thonke
2005-07-31 17:42   ` 2.6.13-rc4-mm1 Andrew Morton
2005-07-31 18:25     ` [linux-usb-devel] 2.6.13-rc4-mm1 david-b
2005-07-31 23:02       ` Greg KH
2005-08-01  2:02         ` david-b
2005-07-31 16:44 ` 2.6.13-rc4-mm1 Randy.Dunlap
2005-08-01  0:38 ` 2.6.13-rc4-mm1 Jesus Delgado
2005-08-01  0:49   ` 2.6.13-rc4-mm1 Andrew Morton
2005-08-01  5:52 ` 2.6.13-rc4-mm1 Alexandre Buisse
2005-08-01  7:03   ` 2.6.13-rc4-mm1 David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2005-08-01 17:26 2.6.13-rc4-mm1 Aleksey Gorelov

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=200507311351.05641.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@osdl.org \
    --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