public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkh@osg.samsung.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: [GIT PULL] Kselftest updates for 3.20-rc1
Date: Mon, 09 Feb 2015 18:02:24 -0700	[thread overview]
Message-ID: <54D958A0.1020404@osg.samsung.com> (raw)
In-Reply-To: <1423529039.19657.6.camel@ellerman.id.au>

On 02/09/2015 05:43 PM, Michael Ellerman wrote:
> On Mon, 2015-02-09 at 17:36 -0700, Shuah Khan wrote:
>> On 02/09/2015 05:30 PM, Michael Ellerman wrote:
>>> On Mon, 2015-02-09 at 11:36 -0700, Shuah Khan wrote:
>>>> Hi Linus,
>>>>
>>>> Please pull the following Kselftest updates for 3.20-rc1
>>>>
>>>> thanks,
>>>> -- Shuah
>>>>
>>>> The following changes since commit 97bf6af1f928216fd6c5a66e8a57bfa95a659672:
>>>>
>>>>   Linux 3.19-rc1 (2014-12-20 17:08:50 -0800)
>>>>
>>>> are available in the git repository at:
>>>>
>>>>   git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
>>>> tags/linux-kselftest-3.20-rc1
>>>>
>>>> for you to fetch changes up to 6ddf898c23d62c974e148efd9e509731324a167a:
>>>>
>>>>   selftests/exec: Check if the syscall exists and bail if not
>>>> (2015-02-04 10:17:35 -0700)
>>>>
>>>> ----------------------------------------------------------------
>>>> Kselftest updates for 3.20-rc1
>>>>
>>>> This update adds:
>>>> - Kselftest install target feature
>>>> - Fix for selftests/exec test
>>>>
>>>> ----------------------------------------------------------------
>>>> Michael Ellerman (1):
>>>>       selftests/exec: Check if the syscall exists and bail if not
>>>>
>>>> Shuah Khan (20):
>>>>       selftests/breakpoints: add install target to enable test install
>>>>       selftests/cpu-hotplug: add install target to enable test install
>>>>       selftests/efivarfs: add install target to enable test install
>>>>       selftests/firmware: add install target to enable test install
>>>>       selftests/ftrace: add install target to enable test install
>>>>       selftests/ipc: add install target to enable test install
>>>>       selftests/kcmp: add install target to enable test install
>>>>       selftests/memfd: add install target to enable test install
>>>>       selftests/memory-hotplug: add install target to enable test install
>>>>       selftests/mount: add install target to enable test install
>>>>       selftests/mqueue: add install target to enable test install
>>>>       selftests/net: add install target to enable test install
>>>>       selftests/ptrace: add install target to enable test install
>>>>       selftests/size: add install target to enable test install
>>>>       selftests/sysctl: add install target to enable test install
>>>>       selftests/timers: add install target to enable test install
>>>>       selftests/user: add install target to enable test install
>>>>       selftests/vm: add install target to enable test install
>>>>       selftests: add install target to enable test install
>>>>       kbuild: add a new kselftest_install make target to install selftests
>>>
>>>
>>> I don't understand why you insist on merging this series with the logic copied
>>> 18 times.
>>>
>>> I'm happy to tweak my series that uses an include file, but I don't see the
>>> point of merging this series first when almost every line will be removed when
>>> my series goes in.
>>
>> Please work on the suggestions I made and rework the patches
>> and resend. As I mentioned earlier, I want to enable this work
>> and them make improvements.
> 
> Yes I would like install to work to. I'd also like it to work for the powerpc
> tests you ignored. But I don't want it to involve copying the same logic into
> every Makefile in the tree.

Michael,

powerpc tests aren't ignored. They are in the list to do as
the next step.

> 
> My series was sent over a month ago, with plenty of time for you to merge it
> instead of this cut-and-paste solution.

I asked you to re-work the patches based on my suggestions
and resend. I didn't see any patches from you that addressed
the comments. I can't merge the patches you sent without
addressing the comments.

I want to get this feature implemented in this series as the
first step and then make improvements that are isolated to the
selftests makefile hierarchy. This series I am requesting to be
pulled in has been in progress for a while now and the series is
v4.

Please plan upon re-working resending the patches for the next
release.

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-02-10  1:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 18:36 [GIT PULL] Kselftest updates for 3.20-rc1 Shuah Khan
2015-02-10  0:30 ` Michael Ellerman
2015-02-10  0:36   ` Shuah Khan
2015-02-10  0:43     ` Michael Ellerman
2015-02-10  1:02       ` Shuah Khan [this message]
2015-02-10  3:16         ` Michael Ellerman
2015-03-02 21:19           ` Dave Jones
2015-03-02 21:27             ` Shuah Khan
2015-03-03  0:53             ` Michael Ellerman
2015-02-20 16:00 ` Shuah Khan

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=54D958A0.1020404@osg.samsung.com \
    --to=shuahkh@osg.samsung.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@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