public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkh@osg.samsung.com>
To: Dave Jones <davej@codemonkey.org.uk>,
	Michael Ellerman <mpe@ellerman.id.au>,
	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, 02 Mar 2015 14:27:03 -0700	[thread overview]
Message-ID: <54F4D5A7.8040801@osg.samsung.com> (raw)
In-Reply-To: <20150302211947.GA2184@codemonkey.org.uk>

On 03/02/2015 02:19 PM, Dave Jones wrote:
> On Tue, Feb 10, 2015 at 02:16:05PM +1100, Michael Ellerman wrote:
>  
>  > > 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
>  > > >>>>
>  > > >>> ...
>  > > >>>
>  > > >>> 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.
>  > > 
>  > > > 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.
>  > 
>  > Your comments were "please rebase on my series", and as I explained that is
>  > pointless because my series replaces your series.
> 
> Michael's series also has a bunch of features this pull doesn't.
> I had started implementing some of these features myself before realizing
> this stuff was in limbo. (Especially the ability to install to a
> different directory: our use case involves packaging up the latest
> selftests for use to be run against a long-term stable kernel).
> 
> What needs to happen to unblock this, given that nothing has been
> merged so far.
> 
> Working on selftests is sort of frustrating with all this stuff pending
> given the potential conflicts.
> 

Dave,

At the moment I am working on an approach that doesn't require
changes to Makefiles. This pull request being in limbo game me
a chance to regroup and come up with a simpler approach. Michael's
work is based on Makefile changes as well.

Please give me couple of days and I will send out patches that add
install, packaging support. I am handling this as tools at the top
level that don't depend on any existing Makefiles targets.

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-03-02 21:27 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
2015-02-10  3:16         ` Michael Ellerman
2015-03-02 21:19           ` Dave Jones
2015-03-02 21:27             ` Shuah Khan [this message]
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=54F4D5A7.8040801@osg.samsung.com \
    --to=shuahkh@osg.samsung.com \
    --cc=davej@codemonkey.org.uk \
    --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