linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Rice <rob.rice@broadcom.com>
To: linux-crypto@vger.kernel.org
Subject: arm64 broken
Date: Wed, 11 Jan 2017 13:37:19 -0500	[thread overview]
Message-ID: <0795D328-B031-4EFA-AA0B-603B66F9F035@broadcom.com> (raw)

I’m working on updating a patchset. The master branch in crypto-2.6 doesn’t compile for ARM64. The first couple errors are listed below. A colleague believes that the following commit in rc2 fixes the problem.

commit b4b8664d291ac1998e0f0bcdc96b6397f0fe68b3
Author: Al Viro <viro@zeniv.linux.org.uk <mailto:viro@zeniv.linux.org.uk>>
Date:   Mon Dec 26 04:10:19 2016 -0500

    arm64: don't pull uaccess.h into *.S
    
    Split asm-only parts of arm64 uaccess.h into a new header and use that
    from *.S.
    
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk <mailto:viro@zeniv.linux.org.uk>>

Any chance we could either pull in the fix or move to rc2?

Thanks,

Rob
 

  AS      arch/arm64/kernel/entry.o
In file included from ./include/linux/sched.h:17:0,
                 from ./include/linux/uaccess.h:4,
                 from arch/arm64/kernel/entry.S:34:
./include/linux/kernel.h:49:0: warning: "ALIGN" redefined
 #define ALIGN(x, a)  __ALIGN_KERNEL((x), (a))
 ^
In file included from arch/arm64/kernel/entry.S:22:0:
./include/linux/linkage.h:78:0: note: this is the location of the previous definition
 #define ALIGN __ALIGN
 ^
In file included from ./include/linux/time.h:7:0,
                 from ./include/uapi/linux/timex.h:56,
                 from ./include/linux/timex.h:56,
                 from ./include/linux/sched.h:19,
                 from ./include/linux/uaccess.h:4,
                 from arch/arm64/kernel/entry.S:34:
./include/linux/time64.h:36:0: warning: "NSEC_PER_SEC" redefined
 #define NSEC_PER_SEC 1000000000L

             reply	other threads:[~2017-01-11 18:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 18:37 Rob Rice [this message]
2017-01-12  7:50 ` arm64 broken Herbert Xu

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=0795D328-B031-4EFA-AA0B-603B66F9F035@broadcom.com \
    --to=rob.rice@broadcom.com \
    --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;
as well as URLs for NNTP newsgroup(s).