From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: trivial@kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH]crypto/Kconfig update broken web addresses.
Date: Sat, 11 Sep 2010 20:31:33 -0700 [thread overview]
Message-ID: <4C8C4995.9060703@gmail.com> (raw)
In-Reply-To: <20100912024323.GA22244@gondor.apana.org.au>
On 09/11/2010 07:43 PM, Herbert Xu wrote:
> On Mon, Sep 06, 2010 at 09:16:59PM -0700, Justin P. Mattock wrote:
>> Below is a patch to update the broken web addresses, in crypto/*
>> that I could locate. Some are just simple typos that needed to be
>> fixed, and some had a change in location altogether..
>> let me know if any of them need to be changed and such.
>>
>> Signed-off-by: Justin P. Mattock<justinmattock@gmail.com>
>
> Patch applied. Thanks!
cool...
Justin P. Mattock
prev parent reply other threads:[~2010-09-12 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 4:16 [PATCH]crypto/Kconfig update broken web addresses Justin P. Mattock
2010-09-12 2:43 ` Herbert Xu
2010-09-12 3:31 ` Justin P. Mattock [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=4C8C4995.9060703@gmail.com \
--to=justinmattock@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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;
as well as URLs for NNTP newsgroup(s).