Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S265537AbSLCTj5>; Tue, 3 Dec 2002 14:39:57 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S265470AbSLCTj5>; Tue, 3 Dec 2002 14:39:57 -0500
Received: from hq.pm.waw.pl ([195.116.170.10]:47234 "EHLO hq.pm.waw.pl")
	by vger.kernel.org with ESMTP id <S265537AbSLCTj4>;
	Tue, 3 Dec 2002 14:39:56 -0500
To: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] generic HDLC update for 2.4.21-pre
References: <m3el91jiyg.fsf@defiant.pm.waw.pl>
	<20021202192014.A20163@electric-eye.fr.zoreil.com>
From: Krzysztof Halasa <khc@pm.waw.pl>
Date: 02 Dec 2002 23:52:53 +0100
In-Reply-To: <20021202192014.A20163@electric-eye.fr.zoreil.com>
Message-ID: <m3k7ism3sq.fsf@defiant.pm.waw.pl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 636
Lines: 11

Francois Romieu <romieu@fr.zoreil.com> writes:

> I'd rather avoid pushing the 2.5.x core code for the dscc4 chipset in
> 2.4 now as some side of it still suck. Is it fine to wait for me to 
> update current 2.4.x dscc4 code to new api ? ETA = now + a few days at 
> worst.

I can see no problem with that, as long as we are at early 2.4.21 stages.
-- 
Krzysztof Halasa
Network Administrator
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/