From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org,
Sebastian Siewior <linux-crypto@ml.breakpoint.cc>
Subject: Re: [1/1 take 2] HIFN: preliminary HIFN 795x driver for new async cryptoapi.
Date: Fri, 22 Jun 2007 17:32:06 +0400 [thread overview]
Message-ID: <20070622133205.GA28828@2ka.mipt.ru> (raw)
In-Reply-To: <20070622123731.GB29919@gondor.apana.org.au>
On Fri, Jun 22, 2007 at 08:37:31PM +0800, Herbert Xu (herbert@gondor.apana.org.au) wrote:
> On Fri, Jun 22, 2007 at 03:58:59PM +0400, Evgeniy Polyakov wrote:
> >
> > > The crypto_alg object should contain a back pointer to the device.
> > > In setkey, you have access to a tfm object which has a pointer to
> > > the crypto_alg object.
> >
> > crypto_alg does not contain it, or do I miss something?
>
> You're right that it's not there as such. However, there's
> nothing stopping you from allocating struct crypto_alg + ctx
> and putting your pointer there.
Argh, I understand now. I will create an access wrapper in HIFN driver
for such access for now, if there will be some API changes it will be
possible to rewrite.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-06-22 13:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 13:42 [1/1 take 2] HIFN: preliminary HIFN 795x driver for new async cryptoapi Evgeniy Polyakov
2007-06-05 12:56 ` Sebastian Siewior
2007-06-05 13:07 ` Evgeniy Polyakov
2007-06-05 15:02 ` Evgeniy Polyakov
2007-06-22 7:34 ` Herbert Xu
2007-06-22 11:58 ` Evgeniy Polyakov
2007-06-22 12:37 ` Herbert Xu
2007-06-22 13:32 ` Evgeniy Polyakov [this message]
2007-06-09 5:02 ` Herbert Xu
2007-06-22 7:28 ` Herbert Xu
2007-06-22 11:57 ` Evgeniy Polyakov
2007-06-22 12:29 ` Sebastian Siewior
2007-06-22 12:36 ` Herbert Xu
2007-06-22 12:39 ` Evgeniy Polyakov
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=20070622133205.GA28828@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@ml.breakpoint.cc \
--cc=linux-crypto@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