Re: CCID3 and CCID4 share code status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Quoting Łeandro Sales:
|  I'm organizing the code according to arnaldo and gerrit
|  suggestions, to use a separated source file, which I named it for
|  ccid34_commons.c/h and link it in the Makefile of ccids/lib via trfc
|  module, is this the correct way gerrit, accoding to your suggestion?
Please ask Arnaldo in these matters - he knows that better than me.
I think you shouldn't feel constrained at the moment, just to get it working.

But it may make sense to consider the library - when it really only has generic
functions - to be put into the test tree. That would require agreement from Ian, too.

I'll be sending a brief summary of the API changes which can be used for integrating
new CCIDs for feature-negotiation.
-
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [IETF DCCP]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux