From: Davidlohr Bueso <dave@stgolabs.net>
To: Shuah Khan <shuahkhan@gmail.com>
Cc: "Young, David" <dayoung@akamai.com>,
Greg KH <gregkh@linuxfoundation.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"shuahkh@osg.samsung.com" <shuahkh@osg.samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: selftests: question about git repos containing selftest.
Date: Tue, 09 Dec 2014 12:53:55 -0800 [thread overview]
Message-ID: <1418158435.10123.10.camel@stgolabs.net> (raw)
In-Reply-To: <CAKocOOMiaUDaP=PJ7R9dtsg001eP68hNLyryVQV=yLMC92aeyg@mail.gmail.com>
On Tue, 2014-12-09 at 13:34 -0700, Shuah Khan wrote:
> On Tue, Dec 9, 2014 at 1:25 PM, Young, David <dayoung@akamai.com> wrote:
> > Thanks, I was definitely looking at the master branch of linux-kselftest.
> >
> > There are still more changes in linux-next repo, should those be considered as "in progress"?
> >
>
> Patches in linux-kselftest fixes branch are the ones I included in my
> pull request
> I just sent out. linux-next might have some selftest patches that are part of a
> series that depend on a sub-system API. Maybe that is what you are seeing
> in linux-next.
Is there any reason why Andrew isn't handling kselftests? Considering it
spans multiple subsystems, it seems far more appropriate that way.
next prev parent reply other threads:[~2014-12-09 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 19:22 Young, David
2014-12-09 19:46 ` Greg KH
2014-12-09 20:21 ` Shuah Khan
2014-12-09 20:25 ` Young, David
2014-12-09 20:34 ` Shuah Khan
2014-12-09 20:53 ` Davidlohr Bueso [this message]
2014-12-09 21:08 ` Young, David
2014-12-09 21:27 ` Shuah Khan
2014-12-09 21:29 ` Young, David
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=1418158435.10123.10.camel@stgolabs.net \
--to=dave@stgolabs.net \
--cc=dayoung@akamai.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=shuahkhan@gmail.com \
/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
Powered by JetHome