From: "David S. Miller" <davem@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@oss.sgi.com
Subject: Re: [NET] Allow MD5 to be a module
Date: Thu, 29 Jul 2004 15:57:19 -0700 [thread overview]
Message-ID: <20040729155719.288882b5.davem@redhat.com> (raw)
In-Reply-To: <20040729114052.GA16001@gondor.apana.org.au>
On Thu, 29 Jul 2004 21:40:52 +1000
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> I found that recent 2.6 kernels no longer allowed me to build MD5 as
> a module even though everything that used it were modules (including
> ipv6 and sctp). It turns out that there were boolean options
> selecting MD5 in the Kconfig files. Due to limitations in the current
> kconfig implementation, this forces MD5 to be a boolean as well.
>
> The usual workaround in these cases is to move the selection up
> to the closest tristate. This is what the following patch does.
Applied, thanks Herbert.
prev parent reply other threads:[~2004-07-29 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 11:40 [NET] Allow MD5 to be a module Herbert Xu
2004-07-29 22:57 ` 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=20040729155719.288882b5.davem@redhat.com \
--to=davem@redhat.com \
--cc=herbert@gondor.apana.org.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).