All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Newport <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Re: Sun4c interrupt controller - Sun4d relevance
Date: Mon, 13 Aug 2007 13:24:38 +0000	[thread overview]
Message-ID: <46C05B96.5060909@netunix.com> (raw)
In-Reply-To: <46BF2A25.9090900@netunix.com>

David Miller wrote:

>Tom is absolutely right, the situation is questionable at best,
>so we have to take the safe course of action and now not accept
>contributions from those who have gone so far as to publicly
>state that they've read the Solaris code and thus are tainted.
>
>It's unfortunate, but really there is no other reasonable course
>of action at this point, sorry :-/
>  
>
Whilst I understand your reaction on this one I believe that you are 
being rather harsh on both Mark and Sun.

Would it not be wiser to clarify the conditions under which Sun have  
generously released this information as a reference resource and ask for 
clarification if necessary.

Sun are making great efforts to open up their code and it seems rather 
churlish to imply possible bad faith where none has been shown to exist. 
There can be no harm in asking for clarification and/or permission to 
use this material.



      parent reply	other threads:[~2007-08-13 13:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-12 15:41 Sun4c interrupt controller - Sun4d relevance Chris Newport
2007-08-12 15:59 ` Blue Swirl
2007-08-12 19:01 ` Mark Fortescue
2007-08-12 19:23 ` Chris Newport
2007-08-12 19:27 ` Tom "spot" Callaway
2007-08-12 20:58 ` Mark Fortescue
2007-08-13  1:50 ` David Miller
2007-08-13  1:59 ` David Miller
2007-08-13  2:03 ` David Miller
2007-08-13 13:24 ` Chris Newport [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=46C05B96.5060909@netunix.com \
    --to=crn@netunix.com \
    --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.