From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] ARM: NEON based fast(er) AES in CBC/CTR/XTS modes
Date: Fri, 4 Oct 2013 19:46:26 +0100 [thread overview]
Message-ID: <20131004184625.GS12758@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAKv+Gu9Lnn4=ENMc1Q+9Bkwj1R+2yk91KK1iETaes_OWaTO+fw@mail.gmail.com>
On Fri, Oct 04, 2013 at 08:41:35PM +0200, Ard Biesheuvel wrote:
> On 4 October 2013 20:34, Nicolas Pitre <nicolas.pitre@linaro.org> wrote:
> > On Fri, 4 Oct 2013, Will Deacon wrote:
> [...]
> >>
> >> Why do you consider it unsuitable to ship the perl script with the kernel?
> >> Perl 5 is already documented as a build dependency in Documentation/Changes
> >
> > Do you have an example of something that does require perl to build the
> > kernel on ARM? I was under the impression that people try to avoid it
> > as much as possible in general.
> >
> > I'm personally sitting on the fence between effectively adding a new
> > kernel build dependencies or carrying the output of the perl script.
> > But if the kernel build does already require perl in practice then this
> > might tip the balance.
> >
>
> I like Russell's suggestion the most, in fact. In this case, the build
> time requirement for Perl effectively gets suspended until you start
> making modifications to the perl script, and the relation between the
> .S and the .pl files is made explicit by the make rule.
>
> Should I put the cmd_perl rule in scripts/Makefile.build ? Or can I
> just keep it under arch/arm/crypto ?
Just running through the Makefiles, it seems we have a fair amount
of stuff already using perl in various ways. So I wouldn't worry too
much about where it's placed. It's probably something that should
eventually end up in scripts/ at _some_ point.
next prev parent reply other threads:[~2013-10-04 18:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 21:59 [PATCH v2 0/3] ARM: NEON based fast(er) AES in CBC/CTR/XTS modes Ard Biesheuvel
2013-10-03 21:59 ` [PATCH v2 1/3] ARM: pull in <asm/simd.h> from asm-generic Ard Biesheuvel
2013-10-03 21:59 ` [PATCH v2 2/3] ARM: move AES typedefs and function prototypes to separate header Ard Biesheuvel
2013-10-03 21:59 ` [PATCH v2 3/3] ARM: add support for bit sliced AES using NEON instructions Ard Biesheuvel
2013-10-04 0:38 ` Nicolas Pitre
2013-10-04 17:48 ` [PATCH v2 0/3] ARM: NEON based fast(er) AES in CBC/CTR/XTS modes Will Deacon
2013-10-04 18:04 ` Ard Biesheuvel
2013-10-04 18:23 ` Russell King - ARM Linux
2013-10-04 18:39 ` Nicolas Pitre
2013-10-04 18:34 ` Nicolas Pitre
2013-10-04 18:40 ` Russell King - ARM Linux
2013-10-04 18:41 ` Ard Biesheuvel
2013-10-04 18:46 ` Russell King - ARM Linux [this message]
2013-10-04 18:57 ` Nicolas Pitre
2013-10-04 18:54 ` Nicolas Pitre
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=20131004184625.GS12758@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).