From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263066AbVF3Uep (ORCPT ); Thu, 30 Jun 2005 16:34:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263051AbVF3UW6 (ORCPT ); Thu, 30 Jun 2005 16:22:58 -0400 Received: from siaag2ae.compuserve.com ([149.174.40.135]:30718 "EHLO siaag2ae.compuserve.com") by vger.kernel.org with ESMTP id S261204AbVF3UGI (ORCPT ); Thu, 30 Jun 2005 16:06:08 -0400 Date: Thu, 30 Jun 2005 16:02:51 -0400 From: Chuck Ebbert <76306.1226@compuserve.com> Subject: Re: -mm -> 2.6.13 merge status (dropped patches?) To: Andrew Morton Cc: linux-netdev , "David S. Miller" , Jeff Garzik , linux-kernel Message-ID: <200506301605_MC3-1-A320-D9D6@compuserve.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 20 Jun 2005 at 23:54:58 -0700, Andrew Morton wrote: > This summarises my current thinking on various patches which are presently > in -mm. I cover large things and small-but-controversial things. Anything > which isn't covered here (and that's a lot of material) is probably a "will > merge", unless it obviously isn't. What happened to: remove-last_rx-update-from-loopback-device.patch It was dropped in 2.6.12-rc1-mm4 with a status of "merged" but it's not in either 2.6.12 or 2.6.13-rc1. And in general, who is tracking whether things are being lost? -- Chuck