public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkh@osg.samsung.com>
To: Tyler Baker <tyler.baker@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Kevin Hilman <khilman@kernel.org>,
	John Stultz <john.stultz@linaro.org>,
	Darren Hart <dvhart@infradead.org>,
	David Herrmann <dh.herrmann@gmail.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 0/6] selftests: improve cross compilation support
Date: Thu, 02 Apr 2015 12:47:59 -0600	[thread overview]
Message-ID: <551D8EDF.8080609@osg.samsung.com> (raw)
In-Reply-To: <551D7B2D.3020703@osg.samsung.com>

On 04/02/2015 11:23 AM, Shuah Khan wrote:
> On 04/02/2015 07:53 AM, Shuah Khan wrote:
>> On 04/01/2015 05:20 PM, Tyler Baker wrote:
>>> This patch set improves cross building functionality by resovling hard coded
>>> assumptions about the compiler used. With this patch set, all but mqueue, 
>>> and kdbus cross build successfully as they must link against a native 
>>> libraries. The hope is tha the above issues can be resolved in future patch 
>>> sets. I have tested this series by building selftests for x86_64, arm and 
>>> arm64 targets.
>>>
>>> This motivation behind this series is to enable the kernelci.org service to
>>> easily build, deploy, and execute selftests on many different processor
>>> architectures without natively compiling them. With the hope of quickly
>>> providing these test results back to the community.
>>>
>>> This series is based on next-20150401.
>>>
>>> Tyler Baker (6):
>>>   selftest/memfd: enable cross compilation
>>>   selftest/kdbus: enable cross compilation
>>>   selftest/mount: enable cross compilation
>>>   selftest/memfd: include default header install path
>>>   selftest/ipc: enable cross compilation
>>>   selftest/mqueue: enable cross compilation
>>>
>>>  tools/testing/selftests/ipc/Makefile    | 6 +-----
>>>  tools/testing/selftests/kdbus/Makefile  | 4 ++--
>>>  tools/testing/selftests/memfd/Makefile  | 8 +++++---
>>>  tools/testing/selftests/mount/Makefile  | 5 +++--
>>>  tools/testing/selftests/mqueue/Makefile | 6 ++++--
>>>  5 files changed, 15 insertions(+), 14 deletions(-)
>>>
>>
>>
>> Tyler,
>>
>> Thanks for getting this work done. It is a bit late for
>> 4.1 and I plan to get these into 4.2.
>>
> 
> After taking a second look at the patches, I want to get
> these into 4.1. It will be nice to enable cross compile
> as well in this release.
> 
> The one patch I won't be able to take it through kselftest
> tree is kdbus for logistical reasons. kdbus is going through
> Greg's tree - one of his many trees :)
> 
> Greg!
> 
> Will you be able to include this kdbus patch in this series
> in your pull request for kdbus. I will reply to the kdbus
> patch in this series and cc you on that. If this doesn't
> work, could you suggest an alternative.
> 

All patches except the kdbus patch are now in linux-kselftest next
for 4.1

thanks,
-- Shuah


-- 
Shuah Khan
Sr. Linux Kernel Developer
Open Source Innovation Group
Samsung Research America (Silicon Valley)
shuahkh@osg.samsung.com | (970) 217-8978

      reply	other threads:[~2015-04-02 18:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 23:20 [PATCH 0/6] selftests: improve cross compilation support Tyler Baker
2015-04-01 23:20 ` [PATCH 1/6] selftest/memfd: enable cross compilation Tyler Baker
2015-04-01 23:20 ` [PATCH 2/6] selftest/kdbus: " Tyler Baker
2015-04-02 17:28   ` Shuah Khan
2015-04-02 22:04     ` Greg Kroah-Hartman
2015-04-03 14:28   ` Greg KH
2015-04-01 23:20 ` [PATCH 3/6] selftest/mount: " Tyler Baker
2015-04-01 23:20 ` [PATCH 4/6] selftest/memfd: include default header install path Tyler Baker
2015-04-01 23:20 ` [PATCH 5/6] selftest/ipc: enable cross compilation Tyler Baker
2015-04-01 23:20 ` [PATCH 6/6] selftest/mqueue: " Tyler Baker
2015-04-02 13:53 ` [PATCH 0/6] selftests: improve cross compilation support Shuah Khan
2015-04-02 17:19   ` Tyler Baker
2015-04-02 17:23   ` Shuah Khan
2015-04-02 18:47     ` 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=551D8EDF.8080609@osg.samsung.com \
    --to=shuahkh@osg.samsung.com \
    --cc=dh.herrmann@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.stultz@linaro.org \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=tyler.baker@linaro.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