From: David Miller <davem@davemloft.net>
To: vladislav.yasevich@hp.com
Cc: linux-kernel@vger.kernel.org, herbert@gondor.apana.org.au,
jens.axboe@oracle.com
Subject: Re: [PATCH] [CRYPTO]: Fix hmac_digest from the SG breakage.
Date: Thu, 25 Oct 2007 18:46:54 -0700 (PDT) [thread overview]
Message-ID: <20071025.184654.191409554.davem@davemloft.net> (raw)
In-Reply-To: <4720F775.8030702@hp.com>
From: Vlad Yasevich <vladislav.yasevich@hp.com>
Date: Thu, 25 Oct 2007 16:07:17 -0400
> Crypto now uses SG helper functions. Fix hmac_digest to use those
> functions correctly and fix the oops associated with it.
>
> Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
Since I keep hitting this when I try to test IPSEC on my systems
I'm going to apply this to my net-2.6 tree.
Herbert, I hope you don't mind :-)
next prev parent reply other threads:[~2007-10-26 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 20:07 [PATCH] [CRYPTO]: Fix hmac_digest from the SG breakage Vlad Yasevich
2007-10-26 1:46 ` David Miller [this message]
2007-10-26 2:42 ` Herbert Xu
2007-10-26 13:43 ` Vlad Yasevich
2007-10-26 13:52 ` Herbert Xu
2007-10-26 16:59 ` Jens Axboe
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=20071025.184654.191409554.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vladislav.yasevich@hp.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