All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Anton Blanchard <anton@samba.org>
Cc: benh@kernel.crashing.org, paulus@samba.org,
	nfont@linux.vnet.ibm.com, mhcerri@linux.vnet.ibm.com,
	herbert@gondor.apana.org.au, davem@davemloft.net,
	linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto/nx: disable NX on little endian builds
Date: Sat, 14 Jun 2014 05:48:14 +0200	[thread overview]
Message-ID: <201406140548.14201.marex@denx.de> (raw)
In-Reply-To: <20140607113334.474343b8@kryten>

On Saturday, June 07, 2014 at 03:33:34 AM, Anton Blanchard wrote:
> The NX driver has endian issues so disable it for now.
> 
> Signed-off-by: Anton Blanchard <anton@samba.org>

What kind of issues ? Are they hard to fix ?

Best regards,
Marek Vasut

WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: Anton Blanchard <anton@samba.org>
Cc: herbert@gondor.apana.org.au, linuxppc-dev@lists.ozlabs.org,
	paulus@samba.org, linux-crypto@vger.kernel.org,
	nfont@linux.vnet.ibm.com, mhcerri@linux.vnet.ibm.com,
	davem@davemloft.net
Subject: Re: [PATCH] crypto/nx: disable NX on little endian builds
Date: Sat, 14 Jun 2014 05:48:14 +0200	[thread overview]
Message-ID: <201406140548.14201.marex@denx.de> (raw)
In-Reply-To: <20140607113334.474343b8@kryten>

On Saturday, June 07, 2014 at 03:33:34 AM, Anton Blanchard wrote:
> The NX driver has endian issues so disable it for now.
> 
> Signed-off-by: Anton Blanchard <anton@samba.org>

What kind of issues ? Are they hard to fix ?

Best regards,
Marek Vasut

  reply	other threads:[~2014-06-14  3:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-07  1:33 [PATCH] crypto/nx: disable NX on little endian builds Anton Blanchard
2014-06-14  3:48 ` Marek Vasut [this message]
2014-06-14  3:48   ` Marek Vasut

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=201406140548.14201.marex@denx.de \
    --to=marex@denx.de \
    --cc=anton@samba.org \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mhcerri@linux.vnet.ibm.com \
    --cc=nfont@linux.vnet.ibm.com \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.