All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@avtrex.com>
Cc: linux-mips@linux-mips.org
Subject: Re: What are the criteria for adding a port to linux-mips...
Date: Wed, 16 Nov 2005 15:17:59 +0000	[thread overview]
Message-ID: <20051116151758.GF3229@linux-mips.org> (raw)
In-Reply-To: <437A5287.9030506@avtrex.com>

On Tue, Nov 15, 2005 at 01:26:31PM -0800, David Daney wrote:

> As you probably know I posted patches for my ATI Xilleon port to this 
> list several weeks ago.  I am in the process of incorporating changes 
> based on the feedback I received.
> 
> I guess my question is fairly simple:
> 
> What hurdles must I overcome in order to get the port added to linux-mips?

I'm trying to handle this no different than Linus or the other subsystem
maintainers.  So, basically:

 - Code should comply to Documentation/CodingStyle
 - Code must be maintainable.
 - There probably will be issues raised when posting patches.  Fix them ...
 - In general I won't consider patches for "one of" ports.
   (You asked a general question, so this is a general answer.  Obviously
   this point isn't a problem for a SOC such as the Xilleon.)
 - A platform is worthless without drivers, so I want to see drivers in a
   shape where they're at least reasonably close to acceptable by the
   respective subsystem maintainers.
 - In the past it happened several times that people sent me their patches,
   I applied them and that's about the last I ever heared and so without
   no hardware, not hardware documentation and as always not enough time
   code starts bitrotting away.  I would realliy appreciate if in the
   future submitters would make an attempt to invest a little work it takes
   to keep their submitted code alive ...

  Ralf

      reply	other threads:[~2005-11-16 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 21:26 What are the criteria for adding a port to linux-mips David Daney
2005-11-16 15:17 ` Ralf Baechle [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=20051116151758.GF3229@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.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.