The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] better CRYPTO_AES <-> CRYPTO_AES_586 dependencies
Date: Tue, 8 Mar 2005 19:50:25 +0000 (UTC)	[thread overview]
Message-ID: <d0kvm1$j1b$1@terminus.zytor.com> (raw)
In-Reply-To: 20050225222938.GG3311@stusta.de

Followup to:  <20050225222938.GG3311@stusta.de>
By author:    Adrian Bunk <bunk@stusta.de>
In newsgroup: linux.dev.kernel
> > 
> > Wouldn't the 586 one also work on x86_64?
> 
> I'd assume yes.
> 
> But the CRYPTO_AES_586 were already this way, and since I don't know the 
> history of these dependencies this isn't changed by my patch.
> 

Anything written in assembly would have to be specifically adjusted to
work on x86-64 (different ABI, 64-bit pointers, etc.)

	-hpa

      reply	other threads:[~2005-03-08 20:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25 21:46 [2.6 patch] better CRYPTO_AES <-> CRYPTO_AES_586 dependencies Adrian Bunk
2005-02-25 22:00 ` James Morris
2005-02-25 22:08 ` Chris Friesen
2005-02-25 22:29   ` Adrian Bunk
2005-03-08 19:50     ` H. Peter Anvin [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='d0kvm1$j1b$1@terminus.zytor.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@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