linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
	Valentin Rothberg <valentinrothberg@gmail.com>,
	Dan Carpenter <error27@gmail.com>, Mel Gorman <mgorman@suse.de>,
	Steven Rostedt <rostedt@goodmis.org>,
	Johannes Thumshirn <jthumshirn@suse.de>,
	Konstantin Ryabitsev <mricon@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Lars Kurth <lars.kurth.xen@gmail.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Robert Schweikert <rjschwei@suse.com>,
	ms@suse.de, Juergen Gross <jgross@suse.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Joerg Roedel <jroedel@suse.de>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: Wiki for automatic reports / fixes
Date: Mon, 12 Oct 2015 12:55:41 -0700	[thread overview]
Message-ID: <CAB=NE6WYUHTsD1vMTYPmECmDM1khu4M4C+GW+MAf7UCuJmdp0g@mail.gmail.com> (raw)
In-Reply-To: <CAB=NE6UR2_SQTxTe2E50fEGDg49F_jtYpbtcz90YdeKiJO5Tmg@mail.gmail.com>

On Mon, Oct 5, 2015 at 10:03 AM, Luis R. Rodriguez
<mcgrof@do-not-panic.com> wrote:
> On Mon, Oct 5, 2015 at 9:56 AM, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
>> Luis R. Rodriguez writes ("Wiki for automatic reports / fixes"):
>> [...]
>>>  While discussing expectations and information about
>>> reports over these with Valentin it occurred to me information about
>>> all these may be scattered separately and some developers may be
>>> surprised when they first get reports / fixes from these sorts of
>>> testing systems and that perhaps it may be useful if we had a single
>>> wiki entry point where we could refer folks to the different ongoing
>>> testing infrastructures out there working upstream.
>>>
>>> If we could piggy back off of an already existing wiki then great, but
>>> if not I was thinking something off of wiki.kernel.org might be good.
>>> How about tests.wiki.kernel.org ? If such projects don't have a wiki
>>> they could perhaps use pages off of tests.wiki.kernel.org to elaborate
>>> and set expectations straight. Thoughts?
>>
>> To clarify what I think you are suggesting, is to create a new wiki or
>> wiki page which gives information about automatic tests that are
>> performed on upstream (or going-upstream) Linux branches ?
>
> That's right, as it stands we have a slew of folks doing a series of
> battery of tests on either linux-next or other branches, and
> developers / maintainers get e-mails about this. Typically one becomes
> aware of these tests through experience and in dealing with reports
> but other times one may not even be aware of ongoing effort on this
> front, such was the case of Valentin's dead code analysis with
> undertaker. Knowing what existing work is being done can and could be
> used can also save people from re-inventing the wheel, but also and
> most importantly collaborate.
>
>> I think this is a good idea.  I'm not sure how much information we
>> need for each tester, but a page for each would be about right.
>
> Sure, I figure if each tester framework has its own dedicated page we
> can at least refer to it, but a basic page which describes general
> coverage / mailing lists / contact info / and what to expect might be
> useful. As it stands most of this is just tribal knowledge.

OK I'll poke and see if we can get this created.

 Luis

  reply	other threads:[~2015-10-12 19:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 19:19 Wiki for automatic reports / fixes Luis R. Rodriguez
2015-10-05 16:56 ` Ian Jackson
2015-10-05 17:03   ` Luis R. Rodriguez
2015-10-12 19:55     ` Luis R. Rodriguez [this message]
2015-10-21 16:13       ` Luis R. Rodriguez

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='CAB=NE6WYUHTsD1vMTYPmECmDM1khu4M4C+GW+MAf7UCuJmdp0g@mail.gmail.com' \
    --to=mcgrof@do-not-panic.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=corbet@lwn.net \
    --cc=error27@gmail.com \
    --cc=fengguang.wu@intel.com \
    --cc=jgross@suse.com \
    --cc=jroedel@suse.de \
    --cc=jthumshirn@suse.de \
    --cc=lars.kurth.xen@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mricon@kernel.org \
    --cc=ms@suse.de \
    --cc=rjschwei@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=valentinrothberg@gmail.com \
    --cc=vkuznets@redhat.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;
as well as URLs for NNTP newsgroup(s).