All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: dccp@vger.kernel.org
Subject: Re: panic on 2.6.24rc5
Date: Wed, 02 Jan 2008 02:40:59 +0000	[thread overview]
Message-ID: <20080102024059.GH25000@ghostprotocols.net> (raw)
In-Reply-To: <200712280016.56674.tomasz@grobelny.oswiecenia.net>

Em Wed, Jan 02, 2008 at 01:57:14AM +0100, Tomasz Grobelny escreveu:
> Dnia Wednesday 02 of January 2008, Arnaldo Carvalho de Melo napisał:
> > If the kernel oopses, if the results are the same or are some problem
> > introduced in the patches by Gerrit. I.e. you would help us to narrow
> > down the problem by trying a binary search of changeset history built
> > kernels.

> Oh, and by the way: does there exist any set of automated tests for dccp? It 
> would be nice to have one, wouldn't it? Otherwise accepting any patch is 
> quite risky...

There are test programs, documented in the wiki, and there is peer
review too :-)

And DCCP on Linux was written in such a way that a large part of its
core engine is actually shared with TCP, benefiting from a much bigger
set of developers and testers.

But please feel free to add more automated tests, it'll benefit us all.

- Arnaldo

  parent reply	other threads:[~2008-01-02  2:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-27 23:16 panic on 2.6.24rc5 Tomasz Grobelny
2007-12-30 15:18 ` Tomasz Grobelny
2008-01-01 19:04 ` Arnaldo Carvalho de Melo
2008-01-01 21:30 ` Tomasz Grobelny
2008-01-02  0:03 ` Arnaldo Carvalho de Melo
2008-01-02  0:57 ` Tomasz Grobelny
2008-01-02  2:40 ` Arnaldo Carvalho de Melo [this message]
2008-01-07 13:41 ` Gerrit Renker
2008-01-07 16:56 ` Gerrit Renker
2008-03-06 20:57 ` Tomasz Grobelny
2008-03-07 12:16 ` Gerrit Renker
2008-03-07 14:52 ` Tomasz Grobelny
2008-03-07 16:09 ` Gerrit Renker

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=20080102024059.GH25000@ghostprotocols.net \
    --to=acme@redhat.com \
    --cc=dccp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.