All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jurij Smakov <jurij@wooyd.org>
To: sparclinux@vger.kernel.org
Subject: Re: debian unusable on niagara
Date: Sat, 02 May 2009 20:56:24 +0000	[thread overview]
Message-ID: <20090502205624.GA14370@droopy.oc.cox.net> (raw)
In-Reply-To: <20090423.070943.158757350.davem@davemloft.net>

On Sat, May 02, 2009 at 01:14:49PM -0700, David Miller wrote:
> From: Jurij Smakov <jurij@wooyd.org>
> Date: Sat, 2 May 2009 18:04:28 +0100
> 
> > There is a bug filed for that (http://bugs.debian.org/525958), however
> > I don't know what effect removal of this driver will have on machines
> > which do not have another console (like no framebuffer device). I would
> > like to ask people to test this change before uploading it into the
> > archive.
> 
> Would you stop with this?
> 
> We have a driver for every conceivable console device on sparc,
> framebuffer, serial, or otherwise.
> 
> We know this will fix real bugs and increase the bootup time on
> niagara by a factor of 10.
> 
> I can't believe discussion is even necessary for this. :-/

I'm doing an honest effort here to make sure that we don't upload
another broken kernel (and I have my reasons, because, for example,
we had XVR-500 and XVR-2500 drivers disabled in Debian kernels until
recently). As I'm doing it in my free time, I don't see why I should
tolerate your tantrums, which seem to happen every time you report
problems with Debian. Sorry for being a bit harsh, but from now on
I'm going to discard any email from you which does not exclusively
contain constructive comments, patches, or other information which
helps to advance our common goal.

Best regards,
-- 
Jurij Smakov                                           jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                      KeyID: C99E03CC

  parent reply	other threads:[~2009-05-02 20:56 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 14:09 debian unusable on niagara David Miller
2009-04-23 14:44 ` David Miller
2009-04-23 14:51 ` David Markey
2009-04-23 15:11 ` Andrew Robert Nicols
2009-04-27 22:29 ` Jurij Smakov
2009-04-28  1:41 ` David Miller
2009-04-28  7:54 ` Jurij Smakov
2009-04-28  7:56 ` David Miller
2009-04-28  7:57 ` David Miller
2009-04-28  8:09 ` Jurij Smakov
2009-04-28  8:44 ` David Miller
2009-05-02 10:25 ` Jurij Smakov
2009-05-02 10:28 ` Jurij Smakov
2009-05-02 16:53 ` David Miller
2009-05-02 17:04 ` Jurij Smakov
2009-05-02 20:14 ` David Miller
2009-05-02 20:56 ` Jurij Smakov [this message]
2009-05-02 21:26 ` David Miller
2009-05-02 22:54 ` Josip Rodin
2009-05-03  0:06 ` David Miller
2009-05-03 11:41 ` Josip Rodin
2009-05-03 13:35 ` Sam Ravnborg
2009-05-03 15:58 ` Josip Rodin
2009-05-03 16:02 ` Sam Ravnborg
2009-05-03 20:09 ` David Miller
2009-05-03 20:10 ` David Miller
2009-05-03 20:11 ` David Miller
2009-05-03 20:13 ` David Miller
2009-05-03 20:44 ` Josip Rodin
2009-05-03 20:50 ` David Miller
2009-05-04  7:40 ` Julien Cristau
2009-05-04  8:29 ` Josip Rodin
2009-05-04  9:12 ` Josip Rodin
2009-05-04  9:34 ` Julien Cristau
2009-05-04  9:57 ` Josip Rodin
2009-05-04 12:15 ` Florian Fainelli
2009-05-04 15:03 ` Josip Rodin
2009-05-04 16:55 ` David Miller
2009-05-04 16:58 ` David Miller
2009-05-04 17:33 ` Josip Rodin
2009-05-04 17:57 ` David Miller

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=20090502205624.GA14370@droopy.oc.cox.net \
    --to=jurij@wooyd.org \
    --cc=sparclinux@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.