From: john slee <indigoid@higherplane.net>
To: linux-kernel@vger.kernel.org
Subject: Re: bk-current __secpath_destroy link error
Date: Wed, 18 Dec 2002 17:55:14 +1100 [thread overview]
Message-ID: <20021218065514.GB18508@higherplane.net> (raw)
In-Reply-To: <20021218065154.GA18508@higherplane.net>
On Wed, Dec 18, 2002 at 05:51:54PM +1100, john slee wrote:
> some lines obviously wrapped. .config attached.
apologies, seems i didn't search archives enough before posting :-(
lesson learned,
j.
--
toyota power: http://indigoid.net/
prev parent reply other threads:[~2002-12-18 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 6:51 bk-current __secpath_destroy link error john slee
2002-12-18 6:55 ` john slee [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=20021218065514.GB18508@higherplane.net \
--to=indigoid@higherplane.net \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.