kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to report bugs for release candidates?
Date: Sun, 26 Mar 2017 10:15:17 +0200	[thread overview]
Message-ID: <20170326081517.GA25270@kroah.com> (raw)
In-Reply-To: <20170325101656.GB29306@wheatley>

On Sat, Mar 25, 2017 at 11:16:56AM +0100, Martin Kletzander wrote:
> Hi everyone,
> 
> I was usually using Bugzilla when I wanted to report something, but what
> if, for example, I can't boot 4.11-rc3?  Is bugzilla fast enough for
> such type of regressions?

Yes, but it's even better if you just use email, sending the crash
information to the developers, and mailing list, where the issue is.
You can use scripts/get_maintainer.pl to find who to send stuff to.

Also, if you can use 'git bisect' to figure out what patch causes the
problem, that's even better.  Then you can email the people who wrote
and approved the patch, and the subsystem mailing list.

thanks,

greg k-h

  reply	other threads:[~2017-03-26  8:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-25 10:16 How to report bugs for release candidates? Martin Kletzander
2017-03-26  8:15 ` Greg KH [this message]
2017-03-26 16:40   ` Nicholas Mc Guire
2017-03-26 11:54 ` Ozgur Karatas

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=20170326081517.GA25270@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).