On Tue, May 12, 2015 at 03:21:12PM -0600, Shuah Khan wrote:
> On 05/12/2015 03:17 PM, Shuah Khan wrote:
> > On 05/12/2015 02:54 PM, Darren Hart wrote:
> >> On 5/12/15, 1:40 PM, "Shuah Khan" wrote:
> >>
> >>> On 05/12/2015 02:15 PM, Darren Hart wrote:
> On 5/12/15, 1:05 PM, "Cyril Hrubis" wro
On 05/12/2015 03:17 PM, Shuah Khan wrote:
> On 05/12/2015 02:54 PM, Darren Hart wrote:
>> On 5/12/15, 1:40 PM, "Shuah Khan" wrote:
>>
>>> On 05/12/2015 02:15 PM, Darren Hart wrote:
On 5/12/15, 1:05 PM, "Cyril Hrubis" wrote:
> Hi!
I'm happy to do that, but I would like to ma
On 05/12/2015 02:54 PM, Darren Hart wrote:
> On 5/12/15, 1:40 PM, "Shuah Khan" wrote:
>
>> On 05/12/2015 02:15 PM, Darren Hart wrote:
>>> On 5/12/15, 1:05 PM, "Cyril Hrubis" wrote:
>>>
Hi!
>>> I'm happy to do that, but I would like to make sure I'm doing the
> right
>>> thing.
>
On 5/12/15, 1:40 PM, "Shuah Khan" wrote:
>On 05/12/2015 02:15 PM, Darren Hart wrote:
>> On 5/12/15, 1:05 PM, "Cyril Hrubis" wrote:
>>
>>> Hi!
>> I'm happy to do that, but I would like to make sure I'm doing the
right
>> thing.
>
> The right thing here is to add -pthread to
On 05/12/2015 02:15 PM, Darren Hart wrote:
> On 5/12/15, 1:05 PM, "Cyril Hrubis" wrote:
>
>> Hi!
> I'm happy to do that, but I would like to make sure I'm doing the
>>> right
> thing.
The right thing here is to add -pthread to CFLAGS which sets both flags
for preprocessor a
On 5/12/15, 1:05 PM, "Cyril Hrubis" wrote:
>Hi!
>> >> I'm happy to do that, but I would like to make sure I'm doing the
>>right
>> >> thing.
>> >
>> >The right thing here is to add -pthread to CFLAGS which sets both flags
>> >for preprocessor and linker (see man gcc).
>>
>> Hi Cyril,
>>
>> Than
Hi!
> >> I'm happy to do that, but I would like to make sure I'm doing the right
> >> thing.
> >
> >The right thing here is to add -pthread to CFLAGS which sets both flags
> >for preprocessor and linker (see man gcc).
>
> Hi Cyril,
>
> Thanks. I read that, and mentioned it, but my concern with -p
On 05/12/2015 11:05 AM, Darren Hart wrote:
> On Tue, May 12, 2015 at 10:47:14AM -0600, Shuah Khan wrote:
>> On 05/12/2015 10:10 AM, Darren Hart wrote:
>>> On 5/12/15, 3:02 AM, "Cyril Hrubis" wrote:
>>>
Hi!
> I'm happy to do that, but I would like to make sure I'm doing the right
> thi
On Tue, May 12, 2015 at 10:47:14AM -0600, Shuah Khan wrote:
> On 05/12/2015 10:10 AM, Darren Hart wrote:
> > On 5/12/15, 3:02 AM, "Cyril Hrubis" wrote:
> >
> >> Hi!
> >>> I'm happy to do that, but I would like to make sure I'm doing the right
> >>> thing.
> >>
> >> The right thing here is to add
On 05/12/2015 10:10 AM, Darren Hart wrote:
> On 5/12/15, 3:02 AM, "Cyril Hrubis" wrote:
>
>> Hi!
>>> I'm happy to do that, but I would like to make sure I'm doing the right
>>> thing.
>>
>> The right thing here is to add -pthread to CFLAGS which sets both flags
>> for preprocessor and linker (see
On 5/12/15, 3:02 AM, "Cyril Hrubis" wrote:
>Hi!
>> I'm happy to do that, but I would like to make sure I'm doing the right
>> thing.
>
>The right thing here is to add -pthread to CFLAGS which sets both flags
>for preprocessor and linker (see man gcc).
Hi Cyril,
Thanks. I read that, and mentione
Hi!
> I'm happy to do that, but I would like to make sure I'm doing the right
> thing.
The right thing here is to add -pthread to CFLAGS which sets both flags
for preprocessor and linker (see man gcc).
--
Cyril Hrubis
chru...@suse.cz
--
To unsubscribe from this list: send the line "unsubscribe l
On Mon, May 11, 2015 at 4:07 PM, Darren Hart wrote:
> On 5/11/15, 3:21 PM, "Shuah Khan" wrote:
>
>No need for a new pull request. Have you seen these errors before:
>
>make[2]: Entering directory
>'/mnt/data/lkml/linux-kselftest/tools/testing/selftests/futex'
>for DIR in funct
On 5/11/15, 3:21 PM, "Shuah Khan" wrote:
No need for a new pull request. Have you seen these errors before:
make[2]: Entering directory
'/mnt/data/lkml/linux-kselftest/tools/testing/selftests/futex'
for DIR in functional; do make -C $DIR all ; done
make[3]: Entering direc
On 05/11/2015 04:21 PM, Shuah Khan wrote:
> On 05/11/2015 03:50 PM, Darren Hart wrote:
>> On 5/11/15, 1:51 PM, "Shuah Khan" wrote:
>>
>>> On 05/11/2015 01:47 PM, Darren Hart wrote:
On 5/11/15, 11:55 AM, "Shuah Khan" wrote:
> On 05/11/2015 12:22 PM, Darren Hart wrote:
>> On 5/11/
On 05/11/2015 03:50 PM, Darren Hart wrote:
> On 5/11/15, 1:51 PM, "Shuah Khan" wrote:
>
>> On 05/11/2015 01:47 PM, Darren Hart wrote:
>>> On 5/11/15, 11:55 AM, "Shuah Khan" wrote:
>>>
On 05/11/2015 12:22 PM, Darren Hart wrote:
> On 5/11/15, 11:06 AM, "Shuah Khan" wrote:
>
>> On
On 5/11/15, 1:51 PM, "Shuah Khan" wrote:
>On 05/11/2015 01:47 PM, Darren Hart wrote:
>> On 5/11/15, 11:55 AM, "Shuah Khan" wrote:
>>
>>> On 05/11/2015 12:22 PM, Darren Hart wrote:
On 5/11/15, 11:06 AM, "Shuah Khan" wrote:
> On 05/08/2015 04:09 PM, Darren Hart wrote:
>> The fu
On 05/11/2015 01:47 PM, Darren Hart wrote:
> On 5/11/15, 11:55 AM, "Shuah Khan" wrote:
>
>> On 05/11/2015 12:22 PM, Darren Hart wrote:
>>> On 5/11/15, 11:06 AM, "Shuah Khan" wrote:
>>>
On 05/08/2015 04:09 PM, Darren Hart wrote:
> The futextest testsuite [1] provides functional, stress,
On 5/11/15, 11:55 AM, "Shuah Khan" wrote:
>On 05/11/2015 12:22 PM, Darren Hart wrote:
>> On 5/11/15, 11:06 AM, "Shuah Khan" wrote:
>>
>>> On 05/08/2015 04:09 PM, Darren Hart wrote:
The futextest testsuite [1] provides functional, stress, and
performance tests for the various futex op
On 05/11/2015 12:22 PM, Darren Hart wrote:
> On 5/11/15, 11:06 AM, "Shuah Khan" wrote:
>
>> On 05/08/2015 04:09 PM, Darren Hart wrote:
>>> The futextest testsuite [1] provides functional, stress, and
>>> performance tests for the various futex op codes. Those tests will be of
>>> more use to fute
On 5/11/15, 11:06 AM, "Shuah Khan" wrote:
>On 05/08/2015 04:09 PM, Darren Hart wrote:
>> The futextest testsuite [1] provides functional, stress, and
>> performance tests for the various futex op codes. Those tests will be of
>> more use to futex developers if they are included with the kernel
>>
On 05/08/2015 04:09 PM, Darren Hart wrote:
> The futextest testsuite [1] provides functional, stress, and
> performance tests for the various futex op codes. Those tests will be of
> more use to futex developers if they are included with the kernel
> source.
>
> Copy the core infrastructure and th
The futextest testsuite [1] provides functional, stress, and
performance tests for the various futex op codes. Those tests will be of
more use to futex developers if they are included with the kernel
source.
Copy the core infrastructure and the functional tests into selftests,
but adapt them for i
On 5/6/15, 10:28 AM, "Shuah Khan" wrote:
>On 03/27/2015 04:17 PM, Darren Hart wrote:
>> The futextest testsuite [1] provides functional, stress, and
>> performance tests for the various futex op codes. Those tests will be of
>> more use to futex developers if they are included with the kernel
>>
On 03/27/2015 04:17 PM, Darren Hart wrote:
> The futextest testsuite [1] provides functional, stress, and
> performance tests for the various futex op codes. Those tests will be of
> more use to futex developers if they are included with the kernel
> source.
>
> Copy the core infrastructure and th
The futextest testsuite [1] provides functional, stress, and
performance tests for the various futex op codes. Those tests will be of
more use to futex developers if they are included with the kernel
source.
Copy the core infrastructure and the functional tests into selftests.
Remove reference to
26 matches
Mail list logo
