From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Jan Steinke <jan.steinke@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Reporting Kernel Bugs
Date: Sat, 15 Oct 2011 14:01:19 +0200 [thread overview]
Message-ID: <201110151401.19977.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1110141321250.24783@chino.kir.corp.google.com>
On piątek, 14 października 2011 o 22:23:57 David Rientjes wrote:
> On Fri, 14 Oct 2011, Jan Steinke wrote:
> > > Just send an e-mail to appropriate mailinglist and CC
> > > responsible maintainer(s).
> > >
> > > That's what many people prefer to bugzilla anyway.
> >
> > How do I know the responsible maintainer(s)? How do I know if the bug is
> > confirmed or accepted?
>
> If you can figure out what subsystem is the likely source of the issue,
> then you can check the MAINTAINERS file for the appropriate people and
> mailing list. If there's a panic or oops, find the source file that is to
> blame and use ./scripts/get_maintainer.pl -f <file>. Otherwise, just
> report some unknown, untriaged error directly to
> linux-kernel@vger.kernel.org and be sure to cc Andrew Morton
> <akpm@linux-foundation.org> who used to go through the kernel.org bugzilla
> quite often and send bug reports in the right direction.
For regression add my address to CC. When bugzilla comes back, then I create
bug entry for regression.
Regards
--
Maciej Rutecki
http://www.mrutecki.pl
prev parent reply other threads:[~2011-10-15 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 18:08 Reporting Kernel Bugs Joseph Salisbury
2011-10-12 18:13 ` Jiri Kosina
2011-10-12 18:17 ` Joseph Salisbury
2011-10-13 12:00 ` Joseph Salisbury
2011-10-13 16:27 ` Jiri Kosina
2011-10-14 20:10 ` Jan Steinke
2011-10-14 20:23 ` David Rientjes
2011-10-15 12:01 ` Maciej Rutecki [this message]
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=201110151401.19977.maciej.rutecki@gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=jan.steinke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.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 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.