From: Daniel Axtens <dja@axtens.net>
To: Matt Brown <matthew.brown.dev@gmail.com>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [v5 1/2] lib/raid6: Build proper files on corresponding arch
Date: Wed, 02 Aug 2017 08:27:43 +1000 [thread overview]
Message-ID: <87bmnysz34.fsf@linkitivity.dja.id.au> (raw)
In-Reply-To: <20170428055809.2675-1-matthew.brown.dev@gmail.com>
Hi Matt,
> --- a/lib/raid6/test/Makefile
> +++ b/lib/raid6/test/Makefile
> @@ -44,10 +44,12 @@ else ifeq ($(HAS_NEON),yes)
> CFLAGS += -DCONFIG_KERNEL_MODE_NEON=1
> else
> HAS_ALTIVEC := $(shell printf '\#include <altivec.h>\nvector int a;\n' |\
> - gcc -c -x c - >&/dev/null && \
> - rm ./-.o && echo yes)
> + gcc -c -x c - >/dev/null && rm ./-.o && echo yes)
>From memory the change here (s/>&/>/) was necessary to get the build to
succeed - did we ever figure out why that was? I'm not enough of a shell
guru to grok the difference. If it's easy to explain it would be good to
put it in the commit message, rather than just saying you fixed an
unspecified bug.
> ifeq ($(HAS_ALTIVEC),yes)
> - OBJS += altivec1.o altivec2.o altivec4.o altivec8.o
> + CFLAGS += -I../../../arch/powerpc/include
> + CFLAGS += -DCONFIG_ALTIVEC
> + OBJS += altivec1.o altivec2.o altivec4.o altivec8.o \
> + vpermxor1.o vpermxor2.o vpermxor4.o vpermxor8.o
You've added vpermxor here, but you don't define them until the next
patch, so the tests will fail. Please move the change to OBJS to the
next patch.
With that change, I'd be happy to formally Review this patch.
Regards,
Daniel
> endif
> endif
> ifeq ($(ARCH),tilegx)
> --
> 2.9.3
next prev parent reply other threads:[~2017-08-01 22:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 5:58 [v5 1/2] lib/raid6: Build proper files on corresponding arch Matt Brown
2017-04-28 5:58 ` [v5 2/2] raid6/altivec: Add vpermxor implementation for raid6 Q syndrome Matt Brown
2017-08-01 23:01 ` Daniel Axtens
2017-08-02 2:04 ` Michael Ellerman
2017-08-02 0:20 ` Daniel Axtens
2017-08-04 1:40 ` Matt Brown
2017-08-01 22:27 ` Daniel Axtens [this message]
2017-08-02 2:00 ` [v5 1/2] lib/raid6: Build proper files on corresponding arch Michael Ellerman
2017-08-04 1:33 ` Matt Brown
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=87bmnysz34.fsf@linkitivity.dja.id.au \
--to=dja@axtens.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matthew.brown.dev@gmail.com \
/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.