All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniela Squassoni <daniela@cyclades.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dscc4 and new Generic HDLC Layer
Date: Mon, 17 Dec 2001 12:43:31 -0300	[thread overview]
Message-ID: <3C1E12A3.5955B8F6@cyclades.com> (raw)
In-Reply-To: <3C19CA22.E604CB32@cyclades.com> <20011214151518.B30306@xyzzy.org.uk> <m31yhwppzq.fsf@defiant.pm.waw.pl>

[-- Attachment #1: Type: text/plain, Size: 728 bytes --]

Krzysztof Halasa wrote:
> 
> Anyway, incremental patch is better, I'm going to submit my paches
> to 2.5 after some features (FR InARP, DCD handling, probably FR bridging)
> are added and tested.
> 
> Seems it's better to include that things in 2.4 when it works fine.
> Especially if all drivers are updated.
> 2.5 first - of course.

How long do you think it will take to include the last changes in 2.4?
Isn't it possible to submit a patch without these new features, just to
speed up this process? Is there anything else that still need to be done
before you submit it?

It seems that there is a consensus that maintaining this out of the
kernel is causing some overhead to the drivers maintainers...

Best regards,

Daniela

[-- Attachment #2: Card for Daniela Squassoni --]
[-- Type: text/x-vcard, Size: 206 bytes --]

begin:vcard 
n:Squassoni;Daniela
x-mozilla-html:FALSE
org:Cyclades;R&D
adr:;;;;;;
version:2.1
email;internet:daniela@cyclades.com
title:Software Engineer
x-mozilla-cpt:;-3392
fn:Daniela Squassoni
end:vcard

      reply	other threads:[~2001-12-17 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-14  9:45 dscc4 and new Generic HDLC Layer Daniela Squassoni
2001-12-14 13:45 ` Francois Romieu
2001-12-14 15:15 ` Bob Dunlop
2001-12-14 13:40   ` Daniela Squassoni
2001-12-15 13:33   ` Krzysztof Halasa
2001-12-17 15:43     ` Daniela Squassoni [this message]

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=3C1E12A3.5955B8F6@cyclades.com \
    --to=daniela@cyclades.com \
    --cc=khc@pm.waw.pl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.