From: Kumar Gala <galak@kernel.crashing.org>
To: Kim Phillips <Kim.Phillips@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: remove tls_ssl_stream descriptor type capability in sec3.3 node
Date: Mon, 17 May 2010 10:51:35 -0500 [thread overview]
Message-ID: <068273A2-8B82-4FE0-BEE8-9FAB152D09D8@kernel.crashing.org> (raw)
In-Reply-To: <20100422192513.27ce5356.kim.phillips@freescale.com>
On Apr 22, 2010, at 7:25 PM, Kim Phillips wrote:
> Technically, whilst SEC v3.3 h/w honours the tls_ssl_stream descriptor
> type, it lacks the ARC4 algorithm execution unit required to be able
> to execute anything meaningful with it. Change the node to agree with
> the documentation that declares that the sec3.3 really doesn't have such
> a descriptor type.
>
> Reported-by: Haiying Wang <Haiying.Wang@freescale.com>
> Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
> ---
> arch/powerpc/boot/dts/mpc8315erdb.dts | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
applied to next
- k
prev parent reply other threads:[~2010-05-17 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 0:25 [PATCH] powerpc: remove tls_ssl_stream descriptor type capability in sec3.3 node Kim Phillips
2010-05-17 15:51 ` Kumar Gala [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=068273A2-8B82-4FE0-BEE8-9FAB152D09D8@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=Kim.Phillips@freescale.com \
--cc=linuxppc-dev@ozlabs.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