From: "David S. Miller" <davem@redhat.com>
To: rusty@linux.co.intel.com
Cc: miyazawa@linux-ipv6.org, linux-kernel@vger.kernel.org
Subject: Re: Latest bk build error in xfrm.h
Date: Thu, 06 Mar 2003 22:18:42 -0800 (PST) [thread overview]
Message-ID: <20030306.221842.69294793.davem@redhat.com> (raw)
In-Reply-To: <1047000245.4169.45.camel@vmhack>
From: Rusty Lynch <rusty@linux.co.intel.com>
Date: 06 Mar 2003 17:24:04 -0800
There is still a build dependency between the INET_AH/INET_ESP and
CRYPTO_HMAC that the Kconfig does not cover. The following trivial
patch fixes it:
Other way around, these selections are made before crypto's
Kconfig is run so you cannot check this dependency.
The default is properly handled in crypto/Kconfig when these
protocols are defined, you should have a look.
If a user intentionally enabled INET_AH/INET_ESP et al. then forcibly
disobeys the default setting for the necessary crypto options, that is
their problem :-)
prev parent reply other threads:[~2003-03-07 6:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 19:47 Latest bk build error in xfrm.h Rusty Lynch
2003-03-06 21:38 ` Rusty Lynch
2003-03-06 23:27 ` David S. Miller
2003-03-07 0:03 ` David S. Miller
2003-03-07 1:24 ` Rusty Lynch
2003-03-07 6:18 ` 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=20030306.221842.69294793.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miyazawa@linux-ipv6.org \
--cc=rusty@linux.co.intel.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