From: Ian McDonald <imcdnzl@gmail.com>
To: dccp@vger.kernel.org
Subject: Re: [PATCH/RFC]: Re: Problem with feature negotiation
Date: Wed, 15 Feb 2006 01:53:54 +0000 [thread overview]
Message-ID: <cbec11ac0602141753sff04be1j69557bab17d0bf73@mail.gmail.com> (raw)
In-Reply-To: <39e6f6c70602140712k5579e1bfy2445f45e9c97f966@mail.gmail.com>
> Take a look at my tree, I guess its fixed now by setting the defaults according
> to the selection of CCIDs in the kernel config, i.e. if CCID2 is built
> it is the default,
> as the spec states, but if it isn't CCID3 becomes the default and an #error is
> spit if no CCID has been selected for compilation.
>
> Please test and report results, then I'll push for Dave to get it into 2.6.17
>
Tested just fine.
Signed-off-by: Ian McDonald <imcdnzl@gmail.com>
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
Department of Computer Science
University of Waikato
New Zealand
prev parent reply other threads:[~2006-02-15 1:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 15:12 [PATCH/RFC]: Re: Problem with feature negotiation Arnaldo Carvalho de Melo
2006-02-15 1:53 ` Ian McDonald [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=cbec11ac0602141753sff04be1j69557bab17d0bf73@mail.gmail.com \
--to=imcdnzl@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox