All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ian McDonald" <ian.mcdonald@jandi.co.nz>
To: dccp@vger.kernel.org
Subject: Re: Towards the ccid-3 and ccid-4 integration
Date: Wed, 26 Sep 2007 23:41:22 +0000	[thread overview]
Message-ID: <5640c7e00709261641n4efbb0aeq53e396d9af38ea56@mail.gmail.com> (raw)
In-Reply-To: <5bc4c4570709241115u1254baa9j7033d1bdc9dc079@mail.gmail.com>

On 9/27/07, Tommi Saviranta <wnd@iki.fi> wrote:
> On Mon, Sep 24, 2007 at 15:15:57 -0300, ツ Leandro Sales wrote:
> > - Identify and provide common code between ccid-4 and ccid-3.
>
> I'm probably little too much of a need-get-my-hands-dirty kind of guy,
> but I think this part usually works out the best while actually doing
> the split. I don't want to scare people away by telling this, but if I
> was working on the split alone, I'd start by moving everything in
> ccid3.c to lib/ccid3.c, and then moving stuff back to ccid3.c in pieces
> as certain functions would have to be rewritten for CCID 4.
>
Yes it's best to experiment and then tidy later often.

> >   1 - minor functions from ccid-3.c to ccid-3.h and include it (.h) in
> > the ccid-4.c, as suggested by Ian and Arnaldo
> >   2 - for more complex functions, write a dccp_ccid3_lib.ko, as
> > suggested by arnaldo
>
> There is very little more to say about this, really. The code should and
> needs to be shared. I just have this bad feeling that ccid3.c will
> become nothing but a skeleton file that does all the work in
> dccp_ccid3_lib.
>
And that's fine. There will be some methods that are different - like
calculating the ipi - and this would then be in ccid3.c and ccid4.c
but not in dccp_ccid3_lib.c

Ian
-- 
Web1: http://wand.net.nz/~iam4/
Web2: http://www.jandi.co.nz
Blog: http://iansblog.jandi.co.nz

  parent reply	other threads:[~2007-09-26 23:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-24 18:15 Towards the ccid-3 and ccid-4 integration 
2007-09-24 21:35 ` 
2007-09-25  2:45 ` Ian McDonald
2007-09-25  9:01 ` Gerrit Renker
2007-09-26 13:41 ` Tommi Saviranta
2007-09-26 23:41 ` Ian McDonald [this message]
2007-09-26 23:51 ` 
2007-09-27  8:19 ` Gerrit Renker
2007-09-27  8:49 ` Ian McDonald

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=5640c7e00709261641n4efbb0aeq53e396d9af38ea56@mail.gmail.com \
    --to=ian.mcdonald@jandi.co.nz \
    --cc=dccp@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.