From: Shuah Khan <shuahkhan@gmail.com>
To: "Bird, Tim" <Tim.Bird@sonymobile.com>
Cc: "linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [kselftest] kselftest wiki (was RE: Fwd: Rough notes from testing unconference)
Date: Fri, 29 Aug 2014 20:55:08 -0600 [thread overview]
Message-ID: <CAKocOOOqSPGjvJcfn_HFZgbZDRH2WFqpTJVBip2jNfhEDYEv2w@mail.gmail.com> (raw)
In-Reply-To: <F5184659D418E34EA12B1903EE5EF5FD015DCAE7ABB8@seldmbx02.corpusers.net>
On Fri, Aug 29, 2014 at 7:09 PM, Bird, Tim <Tim.Bird@sonymobile.com> wrote:
> On Saturday, August 23, 2014 6:35 AM, Bird, Tim wrote:
>> Also, I've requested a 'test' wiki on kernel.org, where we can place
>> notes, ideas, and lists of things to work on, or things in progress
>> (like possible output format guidelines).
>>
>> I'll let everyone know when the wiki is set up.
>
> There is now a kselftest wiki on kernel.org at:
> https://kselftest.wiki.kernel.org/
>
> I believe anyone with a Linux Foundation account can edit it.
> I have put together a main page, along with a few sub-pages for
> some of the sub-projects (as I call them) that were discussed at
> the kernel summit.
>
> Please feel free to directly edit the wiki, or to let me know if
> there's any content you'd like to see placed on the wiki.
>
Thanks for doing this.
>
> P.S. I have copied lkml and linux-api on this. I believe this is the first
> use of linux-api for discussions about kselftest. If the linux-api maintainers
> would prefer we get our own list, please let me know.
I spoke to a few folks and gave a heads up to Michael Kerrisk about using
linux-api for kselftest - so far no objections to using it. I sent in
a patch adding
entry for Kselftest framework to MAINTAINERS file with linux-api as the
mailing list. I have a git for this:
git git://git.kernel.org/pub/scm/shuah/linux-kselftest
I couldn't edit the wiki to add this detail even after logging into my
LF account.
Might have to request for access perhaps.
thanks,
-- Shuah
next prev parent reply other threads:[~2014-08-30 2:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140819163621.GA15109@linux.vnet.ibm.com>
2014-08-22 14:19 ` [Ksummit-discuss] Fwd: Rough notes from testing unconference Grant Likely
2014-08-22 17:59 ` Shuah Khan
2014-08-22 18:08 ` Amit Kucheria
2014-08-28 21:54 ` Shuah Khan
2014-08-23 13:35 ` Bird, Tim
2014-08-23 21:12 ` Grant Likely
2014-08-30 1:09 ` [Ksummit-discuss] [kselftest] kselftest wiki (was RE: Fwd: Rough notes from testing unconference) Bird, Tim
2014-08-30 2:55 ` Shuah Khan [this message]
2014-08-30 5:15 ` Konstantin Ryabitsev
2014-08-23 8:12 ` [Ksummit-discuss] Fwd: Rough notes from testing unconference Fengguang Wu
2014-08-24 17:12 ` Grant Likely
2014-08-24 18:14 ` Guenter Roeck
2014-08-25 9:23 ` Grant Likely
2014-08-25 10:43 ` Guenter Roeck
2014-08-24 18:15 ` Geert Uytterhoeven
2014-08-24 18:37 ` Guenter Roeck
2014-08-24 18:47 ` Olof Johansson
2014-08-24 19:14 ` Jason Cooper
2014-08-24 19:16 ` Jason Cooper
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=CAKocOOOqSPGjvJcfn_HFZgbZDRH2WFqpTJVBip2jNfhEDYEv2w@mail.gmail.com \
--to=shuahkhan@gmail.com \
--cc=Tim.Bird@sonymobile.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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