From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261680AbVBXA6y (ORCPT ); Wed, 23 Feb 2005 19:58:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261747AbVBXA5n (ORCPT ); Wed, 23 Feb 2005 19:57:43 -0500 Received: from electric-eye.fr.zoreil.com ([213.41.134.224]:21149 "EHLO fr.zoreil.com") by vger.kernel.org with ESMTP id S261748AbVBXA4E (ORCPT ); Wed, 23 Feb 2005 19:56:04 -0500 Date: Thu, 24 Feb 2005 01:52:39 +0100 From: Francois Romieu To: Jeff Garzik Cc: Andrew Morton , Linus Torvalds , Netdev , Linux Kernel Subject: Re: [BK PATCHES] 2.6.x r8169 update Message-ID: <20050224005239.GA2599@electric-eye.fr.zoreil.com> References: <421D141C.4030602@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <421D141C.4030602@pobox.com> User-Agent: Mutt/1.4.1i X-Organisation: Land of Sunshine Inc. Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Jeff Garzik : [...] > Agree it needs fixing, but I actually think the rx-offset stuff is more > urgent than this. For the future, it would be useful for both of us to > have separate r8169-fixes and r8169-cleanups queues. Do you have a synonym/pointer for the rx-offset stuff ? It will help me to rework the flow if you can describe in a few words what you expect wrt fixes/cleanups issue. Don't be shy, I won't use it as a contract set in stone :o) -- Ueimor