public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniela Squassoni <daniela@cyclades.com>
To: Bob Dunlop <bob.dunlop@xyzzy.org.uk>
Cc: Krzysztof Halasa <khc@intrepid.pm.waw.pl>,
	Fran?ois Romieu <romieu@cogenit.fr>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: dscc4 and new Generic HDLC Layer
Date: Fri, 14 Dec 2001 10:40:00 -0300	[thread overview]
Message-ID: <3C1A0130.EE7CEE1A@cyclades.com> (raw)
In-Reply-To: <3C19CA22.E604CB32@cyclades.com> <20011214151518.B30306@xyzzy.org.uk>

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

Bob Dunlop wrote:
> 
> I'm confused.  How was the patch generated ?   How should I apply it ?
> 
> The patch repeats some of Krzystofs changes so I can't apply it over the
> top of his patch but at the same time it doesn't include the changes for
> FarSite, SBE Inc or you own Cyclades cards.  Better to have a patch that
> brings all the drivers up to spec in one hit surely.

This patch was done against the kernel 2.4.17-pre8. All the drivers that
are using the HDLC layer in the kernel source tree have been included.
The farsync.c does not even call the register_hdlc_device routine... 

Let's fix what is already in the kernel source tree first, and then we
can include what is missing (e.g. the PC300 driver and others that
provide separate patches for the HDLC layer), right?!

> 
> Probably too late to get API changes into 2.4.x, but we should get the
> generic HDLC layer into 2.5.x ASAP IMHO.  Then you might be able to argue
> for a backport into 2.4.x in the future.

Why doing that if it is ready for 2.4.x?!
The patch that I've just sent doesn't bring anything really new. It just
fixes what is wrong in the current version. Am I missing something here?

> 
> > I am waiting for the inclusion of these changes in the kernel for months
> > to submmit the PC300 driver, and this delay is causing me troubles,
> > customers complainings, etc.
> 
> Tell me about it :-)  FarSite are having to maintain an extra set of patches
> for customers who need the functionality of the generic layer.
That is exactly what I have to do...

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-14 16:52 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 [this message]
2001-12-15 13:33   ` Krzysztof Halasa
2001-12-17 15:43     ` Daniela Squassoni

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=3C1A0130.EE7CEE1A@cyclades.com \
    --to=daniela@cyclades.com \
    --cc=bob.dunlop@xyzzy.org.uk \
    --cc=khc@intrepid.pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romieu@cogenit.fr \
    /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