From: Florian Mickler <florian@mickler.org>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: bugs/regressions: report in LKML or in bugzilla?
Date: Wed, 8 Dec 2010 11:00:58 +0100 [thread overview]
Message-ID: <20101208110058.15ed7023@schatten.dmk.lab> (raw)
In-Reply-To: <201012072204.36581.Martin@lichtvoll.de>
On Tue, 7 Dec 2010 22:04:30 +0100
Martin Steigerwald <Martin@lichtvoll.de> wrote:
> Am Dienstag 07 Dezember 2010 schrieb Randy Dunlap:
> > On Tue, 7 Dec 2010 16:39:46 +0100 Martin Steigerwald wrote:
> > > [Bug 23642] New: easycap driver fails to compile in 2.6.37-rc3
> > > https://bugzilla.kernel.org/show_bug.cgi?id=23642
> >
> > That one has received attention. I commented on it and I have posted
> > a patch that fixes that particular build problem.
>
> Sorry, I somehow missed that reply. Thanks.
The Bugzilla system did have some hickups in the last months, but seems
stable now. (knock wood)
> > Bugs that are posted to LKML usually are added to the kernel bugzilla
> > by one of the bugzilla maintainers. They would also select the
> > component, so you could just try that route to see if it works better.
>
> Or I create a Bugzilla to save bugzilla maintainers some work and post a
> hint on the mailinglist, too?
>
> Ciao,
Yes, this would be ok. If you do that, it might be useful to also post a
note in the bugzilla report with a reference to the mailinglist-thread
in case a solutions crops up via mail and somehow doesn't make it into
the bugzilla. That makes it easier to decide what to do with a left-over
bugreport 6 months from now.
Regards,
Flo
prev parent reply other threads:[~2010-12-08 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 15:39 bugs/regressions: report in LKML or in bugzilla? Martin Steigerwald
2010-12-07 16:12 ` Eric Dumazet
2010-12-07 21:02 ` Ben Hutchings
2010-12-07 21:28 ` Martin Steigerwald
2010-12-07 21:11 ` Martin Steigerwald
2010-12-07 17:41 ` Randy Dunlap
2010-12-07 21:04 ` Martin Steigerwald
2010-12-08 10:00 ` Florian Mickler [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=20101208110058.15ed7023@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=Martin@lichtvoll.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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