mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkh@osg.samsung.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
	bamvor.zhangjian@huawei.com, Shuah Khan <shuah@kernel.org>
Cc: linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
	khilman@linaro.org, broonie@kernel.org,
	Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH RFC 0/6] enable O and KBUILD_OUTPUT for kselftest
Date: Thu, 17 Nov 2016 17:18:23 -0700	[thread overview]
Message-ID: <aa31a8db-a75f-8a56-8677-23166fb6988d@osg.samsung.com> (raw)
In-Reply-To: <8760nliqxj.fsf@concordia.ellerman.id.au>

On 11/17/2016 05:15 PM, Michael Ellerman wrote:
> Shuah Khan <shuahkh@osg.samsung.com> writes:
> 
>> On 10/21/2016 05:01 AM, bamvor.zhangjian@huawei.com wrote:
>>> From: Bamvor Jian Zhang <bamvor.zhangjian@linaro.org>
>>>
>>> Here is my first version for enabling the KBUILD_OUTPUT for kselftest.
>>> I fix and test all the TARGET in tools/testing/selftest/Makefile. For
>>> ppc, I test through fake target.
> ...
>>>
>>> The last patch introduces the KBUILD_OUTPUT and O for kselftest instead
>>> using the existing kbuild system because user may compile kselftest
>>> directly (make -C tools/testing/selftests).
>>
>> I am planning to get this into 4.10.
>>
>> Michael!
>>
>> Are okay with me taking powerpc tests through kselftest tree?
>> If so could you please give me Ack.
> 
> I already have quite a lot of selftests queued for 4.10, so this will
> conflict badly with those I suspect.

Let me know how bad it is, maybe we can wait on these until 4.11
> 
> If you put this series in a topic branch that we can both merge then
> that will probably be OK.

Once you are done with reviews, we can make a call on whether to merge
them now or later.

> 
> I'd like to review the series first too, will try and get that done
> today.
> 
> cheers
> 

Okay sounds good.

thanks,
-- Shuah

      reply	other threads:[~2016-11-18  0:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21 11:01 bamvor.zhangjian
2016-10-21 11:01 ` [PATCH RFC 1/6] selftests: remove duplicated all and clean target bamvor.zhangjian
2016-11-18 10:31   ` Michael Ellerman
2016-11-18 12:59     ` Zhangjian (Bamvor)
2016-11-21  8:53       ` Michael Ellerman
2016-10-21 11:01 ` [PATCH RFC 2/6] selftests: remove useless TEST_DIRS bamvor.zhangjian
2016-11-18 10:31   ` Michael Ellerman
2016-10-21 11:01 ` [PATCH RFC 3/6] selftests: add default rules for c source file bamvor.zhangjian
2016-11-18 10:57   ` Michael Ellerman
2016-10-21 11:01 ` [PATCH RFC 4/6] selftests: remove CROSS_COMPILE in dedicated Makefile bamvor.zhangjian
2016-11-18 10:58   ` Michael Ellerman
2016-10-21 11:01 ` [PATCH RFC 5/6] selftests: add EXTRA_CLEAN for clean target bamvor.zhangjian
2016-11-18 11:01   ` Michael Ellerman
2016-11-18 12:51     ` Zhangjian (Bamvor)
2016-10-21 11:01 ` [PATCH RFC 6/6] selftests: enable O and KBUILD_OUTPUT bamvor.zhangjian
2016-11-18 11:29   ` Michael Ellerman
2016-11-18 13:03     ` Zhangjian (Bamvor)
2016-10-21 11:11 ` [PATCH RFC 0/6] enable O and KBUILD_OUTPUT for kselftest Bamvor Zhang Jian
2016-11-16 23:57 ` Shuah Khan
2016-11-18  0:15   ` Michael Ellerman
2016-11-18  0:18     ` 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=aa31a8db-a75f-8a56-8677-23166fb6988d@osg.samsung.com \
    --to=shuahkh@osg.samsung.com \
    --cc=bamvor.zhangjian@huawei.com \
    --cc=broonie@kernel.org \
    --cc=khilman@linaro.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=shuah@kernel.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

all inboxes | Powered by JetHome®