linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Keith Curtis <keithcu@gmail.com>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 3.12 released .. and no merge window yet .. and 4.0 plans?
Date: Thu, 07 Nov 2013 11:17:59 +0100	[thread overview]
Message-ID: <527B68D7.2030403@ahsoftware.de> (raw)
In-Reply-To: <CAHW+f2J8L8ys-=Eszf4QQHOkr=vC9nVv63Pz4v_=wZNxWCjDvQ@mail.gmail.com>

Am 06.11.2013 14:42, schrieb Keith Curtis:
> I don't know if you all should spend time working only on bugs, but I
> believe more time should be spent on the bug *list*. There are many
> users patiently waiting for the kernel to work for their computer. The
> pleas for help can be read in the bug database. The data can be used
> to determine the selective places in the code that need more
> brainpower. Send in the cavalry! Some have been waiting for years. I'm
> running into 9 kernel / X bugs on my new Lenovo Yoga 2 with 3.11.6. An
> unprioritized buglist also discourages people from entering new, valid
> ones. As the issue list gets in better shape, things will become a bit
> more relaxed. Quality metrics around bug count and age can be useful.

The problem with many bugs is, that workarounds don't get accepted.

So the situation sometimes is that there is a driver which isn't that 
perfect and when you try to fix something, the patch is refused because 
it is as imperfect as the whole driver (even if the patch would cure 
some problems).
So the only fix which won't be refused is a rewrite of the driver which 
often just isn't what people are willing to do.

Regards,

Alexander Holler


  reply	other threads:[~2013-11-07 10:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04  0:10 Linux 3.12 released .. and no merge window yet .. and 4.0 plans? Linus Torvalds
2013-11-04  3:11 ` Tony Luck
2013-11-04  6:25 ` Ingo Molnar
2013-11-04 19:08   ` Josh Boyer
2013-11-04 19:53     ` Geert Uytterhoeven
2013-11-07  4:40   ` Greg KH
2013-11-07  9:01     ` Ingo Molnar
2013-11-04 17:00 ` Alexander Holler
2013-11-04 19:49   ` Geert Uytterhoeven
2013-11-04 20:16     ` Alexander Holler
2013-11-04 23:02     ` Alexander Holler
2013-11-06 13:42       ` Keith Curtis
2013-11-07 10:17         ` Alexander Holler [this message]
2013-11-15  1:11           ` Keith Curtis
2013-11-04 20:05 ` Olof Johansson
2013-11-04 20:12 ` Hans de Bruin
2013-11-04 21:46 ` Linux 3.12 released " Jan Engelhardt
2013-11-05  5:06   ` Aldo Iljazi
2013-11-05  5:08   ` Alexander Holler
2013-11-04 21:57 ` Linux 3.12 released .. and no merge window yet " One Thousand Gnomes
2013-11-10  4:13 ` Alexandre Oliva

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=527B68D7.2030403@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=keithcu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).