public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <shuah@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
	Fathi Boudra <fathi.boudra@linaro.org>
Cc: Marcin Nowakowski <marcin.nowakowski@imgtec.com>,
	SeongJae Park <sj38.park@gmail.com>,
	linux-kselftest@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Shuah Khan <shuahkh@osg.samsung.com>,
	Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 0/3] kselftest build errors
Date: Mon, 24 Jul 2017 12:28:29 -0600	[thread overview]
Message-ID: <03254abb-bb43-61fd-35f7-e4a7bc38daf7@kernel.org> (raw)
In-Reply-To: <CA+G9fYuYqRNP9nf2m1XaV7MtZdKyKQubpXVR9BFYq_C3xJQnaw@mail.gmail.com>

On 07/12/2017 03:30 AM, Naresh Kamboju wrote:
> Hi Fathi and Shuah,
> 
> On 29 June 2017 at 14:07, Fathi Boudra <fathi.boudra@linaro.org> wrote:
>> On 28 June 2017 at 17:21, Shuah Khan <shuah@kernel.org> wrote:
>>> On 06/28/2017 02:30 AM, Fathi Boudra wrote:
>>>> On 23 June 2017 at 22:44, Shuah Khan <shuah@kernel.org> wrote:
>>>>> On 06/23/2017 04:37 AM, Marcin Nowakowski wrote:
>>>>>> This patch series fixes build errors observed when building net, memfd, gpio and intel_pstate tests
>>>>>>
>>>>>> Marcin Nowakowski (3):
>>>>>>   selftests/{net,memfd}: fix undefined references to external libraries
>>>>>>   selftests/gpio: fix build error
>>>>>>   selftests/intel_pstate: fix undefined reference when building
>>>>>>
>>>>>>  tools/testing/selftests/gpio/Makefile         | 2 +-
>>>>>>  tools/testing/selftests/intel_pstate/Makefile | 2 +-
>>>>>>  tools/testing/selftests/memfd/Makefile        | 4 ++--
>>>>>>  tools/testing/selftests/net/Makefile          | 2 +-
>>>>>>  4 files changed, 5 insertions(+), 5 deletions(-)
>>>>>>
>>>>>
>>>>> Hi Marcin,
>>>>>
>>>>> SeongJae Park sent me fixes for the memfd/net/intel_pstate problems
>>>>> last week. I pulled those in already.
>>>>>
>>>>> The gpio fix is something I need to look at closely to see if this is
>>>>> the way to go. I will get back to you on that.
>>>>
>>>> Any updates on the gpio fix? I've tested it and it works for me.
>>>>
>>>
>>> I haven't decided yet.
>>
>> another alternative is to use realpath:
>> -GPIODIR := ../../../gpio
>> +GPIODIR := $(realpath ../../../gpio)
>>

You are welcome to send a patch.

>> btw, this commit:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=51c6bd7cbe0366b642d8ac90d98739c39ab091a9
>> should be reverted once the build error is addressed because they
>> shouldn't have been there in the first place due to lack of trailing
>> slash in the path.

Yes. This was a temporary solution.

thanks,
-- Shuah
> 
> The current status on linux-next is,
> gpio-mockup-chardev.c building binary failed and shell script not able
> to locate test binary,
> gpio-mockup-chardev: No such file or directory
> 
> Bug link,
> https://bugs.linaro.org/show_bug.cgi?id=3122
> 
> - Naresh
>>
>>> thanks,
>>> -- Shuah
> 
> 

      reply	other threads:[~2017-07-24 18:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 10:37 [PATCH 0/3] kselftest build errors Marcin Nowakowski
2017-06-23 10:37 ` [PATCH 1/3] selftests/{net,memfd}: fix undefined references to external libraries Marcin Nowakowski
2017-06-23 10:37 ` [PATCH 2/3] selftests/gpio: fix build error Marcin Nowakowski
2017-06-28  8:34   ` Fathi Boudra
2017-06-23 10:37 ` [PATCH 3/3] selftests/intel_pstate: fix undefined reference when building Marcin Nowakowski
2017-06-23 19:44 ` [PATCH 0/3] kselftest build errors Shuah Khan
2017-06-28  8:30   ` Fathi Boudra
2017-06-28 14:21     ` Shuah Khan
2017-06-29  8:37       ` Fathi Boudra
2017-07-12  9:30         ` Naresh Kamboju
2017-07-24 18:28           ` Shuah Khan [this message]

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=03254abb-bb43-61fd-35f7-e4a7bc38daf7@kernel.org \
    --to=shuah@kernel.org \
    --cc=fathi.boudra@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=marcin.nowakowski@imgtec.com \
    --cc=naresh.kamboju@linaro.org \
    --cc=shuahkh@osg.samsung.com \
    --cc=sj38.park@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox