linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Cristian Marussi <cristian.marussi@arm.com>,
	linux-kselftest@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Kselftest fixes2 update for Linux 5.5.rc1
Date: Mon, 2 Dec 2019 09:12:48 -0700	[thread overview]
Message-ID: <2b0d6a6e-d135-f5dd-f8e9-74b3130d5e9e@linuxfoundation.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]

Hi Linus,

Please pull this second Kselftest fixes update for Linux 5.5-rc1.

This second Kselftest fixes update for Linux 5.5-rc1 consists of
an urgent revert to fix regression in CI coverage.

diff is attached.

thanks,
-- Shuah

----------------------------------------------------------------

The following changes since commit ed2d8fa734e7759ac3788a19f308d3243d0eb164:

   selftests: sync: Fix cast warnings on arm (2019-11-07 14:54:37 -0700)

are available in the Git repository at:

   git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest 
tags/linux-kselftest-5.5-rc1-fixes2

for you to fetch changes up to f60b85e83659b5fbd3eb2c8f68d33ef4e35ebb2c:

   Revert "selftests: Fix O= and KBUILD_OUTPUT handling for relative 
paths" (2019-11-28 16:27:44 -0700)

----------------------------------------------------------------
linux-kselftest-5.5-rc1-fixes2

This second Kselftest fixes update for Linux 5.5-rc1 consists of
an urgent revert to fix regression in CI coverage.

----------------------------------------------------------------
Shuah Khan (1):
       Revert "selftests: Fix O= and KBUILD_OUTPUT handling for relative 
paths"

  tools/testing/selftests/Makefile | 5 ++---
  1 file changed, 2 insertions(+), 3 deletions(-)

----------------------------------------------------------------

[-- Attachment #2: linux-kselftest-5.5-rc1-fixes2.diff --]
[-- Type: text/x-patch, Size: 802 bytes --]

diff --git a/tools/testing/selftests/Makefile b/tools/testing/selftests/Makefile
index 6e762c42d758..503a93afd452 100644
--- a/tools/testing/selftests/Makefile
+++ b/tools/testing/selftests/Makefile
@@ -86,10 +86,10 @@ override LDFLAGS =
 endif
 
 ifneq ($(O),)
-	BUILD := $(abs_objtree)
+	BUILD := $(O)
 else
 	ifneq ($(KBUILD_OUTPUT),)
-		BUILD := $(abs_objtree)/kselftest
+		BUILD := $(KBUILD_OUTPUT)/kselftest
 	else
 		BUILD := $(shell pwd)
 		DEFAULT_INSTALL_HDR_PATH := 1
@@ -102,7 +102,6 @@ include $(top_srcdir)/scripts/subarch.include
 ARCH           ?= $(SUBARCH)
 export KSFT_KHDR_INSTALL_DONE := 1
 export BUILD
-#$(info abd_objtree = $(abs_objtree) BUILD = $(BUILD))
 
 # build and run gpio when output directory is the src dir.
 # gpio has dependency on tools/gpio and builds tools/gpio

             reply	other threads:[~2019-12-02 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 16:12 Shuah Khan [this message]
2019-12-03  1:50 ` [GIT PULL] Kselftest fixes2 update for Linux 5.5.rc1 pr-tracker-bot

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=2b0d6a6e-d135-f5dd-f8e9-74b3130d5e9e@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=cristian.marussi@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=torvalds@linux-foundation.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).