From: "David S. Miller" <davem@redhat.com>
To: jmorris@intercode.com.au
Cc: akpm@digeo.com, netdev@oss.sgi.com
Subject: Re: [PATCH] Use new kconfig 'select' for networking crypto
Date: Tue, 03 Jun 2003 22:49:25 -0700 (PDT) [thread overview]
Message-ID: <20030603.224925.68063710.davem@redhat.com> (raw)
In-Reply-To: <Mutt.LNX.4.44.0306041222190.28457-100000@excalibur.intercode.com.au>
From: James Morris <jmorris@intercode.com.au>
Date: Wed, 4 Jun 2003 12:28:50 +1000 (EST)
The patch below against recent bk uses the new 'select' feature of
kconfig to configure crypto features for ipsec and ipv6 privacy
extensions.
This should solve a lot of the build problems people have been
having, and it also enables the crypto submenu (which previously
did not work).
Applied, thanks a lot James.
prev parent reply other threads:[~2003-06-04 5:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 2:28 [PATCH] Use new kconfig 'select' for networking crypto James Morris
2003-06-04 5:49 ` David S. Miller [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=20030603.224925.68063710.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@digeo.com \
--cc=jmorris@intercode.com.au \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).