From: Rob Landley <rob@landley.net>
To: Jussi Kivilinna <jussi.kivilinna@iki.fi>
Cc: Kevin Mulvey <kevin@kevinmulvey.net>,
herbert@gondor.hengli.com.au, davem@davemloft.net,
linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, astor@fast.no
Subject: Status of "kernel crypto services" patch? Re: [PATCH] Documentation: "kerneli" typo in description for "Serpent cipher algorithm" Bug #60848
Date: Wed, 02 Oct 2013 13:48:58 -0500 [thread overview]
Message-ID: <1380739738.1974.129@driftwood> (raw)
In-Reply-To: <524C645E.9030800@iki.fi> (from jussi.kivilinna@iki.fi on Wed Oct 2 13:22:22 2013)
On 10/02/2013 01:22:22 PM, Jussi Kivilinna wrote:
> On 02.10.2013 21:12, Rob Landley wrote:
> > On 10/02/2013 11:10:37 AM, Kevin Mulvey wrote:
> >> change kerneli to kernel as well as kerneli.org to kernel.org
> >>
> >> Signed-off-by: Kevin Mulvey <kevin@kevinmulvey.net>
> >
> > There's a bug number for this?
> >
> > Acked, queued. (Although I'm not sure the value of pointing to
> www.kernel.org for this.)
>
> I think kerneli.org is correct.. see old website at
> http://web.archive.org/web/20010201085500/http://www.kerneli.org/
Should I have the update link to the archive.org page, or...?
The above links to http://www.kernel.org/pub/linux/kernel/crypto which
has patches for the 2.5 kernel circa 2003. Did this get merged, or
dropped, or what?
(Documentation maintainership does not mean domain expert in
everything, it's somewhere between librarian and janitor. Please tell
me what to do here.)
Rob
next prev parent reply other threads:[~2013-10-02 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 16:10 [PATCH] Documentation: "kerneli" typo in description for "Serpent cipher algorithm" Bug #60848 Kevin Mulvey
2013-10-02 18:12 ` Rob Landley
2013-10-02 18:22 ` Jussi Kivilinna
2013-10-02 18:34 ` Kevin Mulvey
2013-10-02 18:56 ` Rob Landley
2013-10-02 18:48 ` Rob Landley [this message]
2013-10-03 12:14 ` Status of "kernel crypto services" patch? " Herbert Xu
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=1380739738.1974.129@driftwood \
--to=rob@landley.net \
--cc=astor@fast.no \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=jussi.kivilinna@iki.fi \
--cc=kevin@kevinmulvey.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox