From: "Leonidas S. Barbosa" <leosilva@linux.vnet.ibm.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] Enabling VMX module for PPC64
Date: Fri, 6 Feb 2015 14:41:39 -0200 [thread overview]
Message-ID: <20150206164139.GA13760@bluepex.com> (raw)
In-Reply-To: <1423173503.32511.16.camel@x220>
Thanks for the advices Paul.
Resending patch set as V2.
> > +vmx-crypto-objs := vmx.o aesp8-ppc.o ghashp8-ppc.o aes.o aes_cbc.o aes_ctr.o ghash.o
> > +
> > +ifeq ($(CONFIG_PPC64),y)
>
> Can this test ever fail?
In fact we don't need this first IF, since it already depends on
PPC64.
---
Leonidas.
prev parent reply other threads:[~2015-02-06 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 17:21 [PATCH 7/7] Enabling VMX module for PPC64 Leonidas S. Barbosa
2015-02-05 21:58 ` Paul Bolle
2015-02-06 16:41 ` Leonidas S. Barbosa [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=20150206164139.GA13760@bluepex.com \
--to=leosilva@linux.vnet.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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).