From: Sanidhya Solanki <jpage.lkml@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] Staging: Skein: Moved macros from skein_block.c to header
Date: Sat, 5 Dec 2015 22:25:16 -0500 [thread overview]
Message-ID: <20151205222516.13a8baf6@gmail.com> (raw)
In-Reply-To: <201512060035.GGCfWsZs%fengguang.wu@intel.com>
I disagree with the output of the automaton. Included below are my
compile checks before and after the patch.
The output has been scrubbed to remove information about my file layout.
------------------------------------------------------------------
[~ linux]$ git branch -v
master 31ade3b Linux 4.4-rc3
* pat 31ade3b Linux 4.4-rc3
[~ linux]$ make -j5 drivers/staging/skein/skein_block.o
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CHK include/generated/timeconst.h
CHK include/generated/bounds.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
CC drivers/staging/skein/skein_block.o
[~ linux]$ pwd
~/linux
[~ linux]$ git branch -v
master 31ade3b Linux 4.4-rc3
* pat 31ade3b Linux 4.4-rc3
[~ linux]$ git branch -v
master 31ade3b Linux 4.4-rc3
* pat 4d2271c Staging: Skein: Moved macros from skein_block.c to
header file.
[~ linux]$ pwd
~/linux
[~ linux]$ make -j5 drivers/staging/skein/skein_block.o
CHK include/config/kernel.release
UPD include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
UPD include/generated/utsrelease.h
CHK include/generated/timeconst.h
CHK include/generated/bounds.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
CC drivers/staging/skein/skein_block.o
next prev parent reply other threads:[~2015-12-06 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 11:35 [PATCH] Staging: Skein: Moved macros from skein_block.c to header Sanidhya Solanki
2015-12-05 16:43 ` kbuild test robot
2015-12-06 3:25 ` Sanidhya Solanki [this message]
2015-12-07 6:07 ` Sudip Mukherjee
2015-12-07 10:09 ` Sanidhya Solanki
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=20151205222516.13a8baf6@gmail.com \
--to=jpage.lkml@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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.