linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: hermann pitton <hermann-pitton@arcor.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
	linux-kernel@vger.kernel.org, video4linux-list@redhat.com,
	linux-dvb@linuxtv.org
Subject: Re: NDAs - ANY KNOWN RULES?
Date: Wed, 27 Jun 2007 20:28:34 +0200	[thread overview]
Message-ID: <1182968914.5259.24.camel@pc08.localdom.local> (raw)
In-Reply-To: <1182911833.3201.0.camel@laptopd505.fenrus.org>

Am Dienstag, den 26.06.2007, 19:37 -0700 schrieb Arjan van de Ven:
> > Thanks for your explanations,
> > 
> > but I know for sure it does't work.
> 
> then.. do you have an actual question or are you just trying to troll?
> 
> and yes there have been several such trolls lately on this list, and so
> far your postings have all the signs of being just another one..
> 
> 
> DO NOT FEED THE TROLLS
> 
> 

Hello,

thanks ;), you might help me to decide if somebody abuses a list already
for free advertising or is still contributing.
http://marc.info/?l=linux-video&m=118289479416612&w=2

Sorry, my question is, where one can look up if the pinning of a newer
chip we support is also only under NDA available. Previously often at
least that was public. (examples now saa7131e, tda10046a, tda8275ac1)

If I don't find anything on the web, whom I have to ask that question,
the NDA holder, the manufacturer or do we have a list, because everybody
knows that this can be helpful to identify hardware differences and this
question is always asked already?

Thanks,
Hermann





  reply	other threads:[~2007-06-27 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27  0:03 NDAs - ANY KNOWN RULES? hermann pitton
2007-06-27  0:24 ` Daniel Barkalow
2007-06-27  0:50   ` hermann pitton
2007-06-27  2:37     ` Arjan van de Ven
2007-06-27 18:28       ` hermann pitton [this message]
2007-06-27 18:41         ` Arjan van de Ven

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=1182968914.5259.24.camel@pc08.localdom.local \
    --to=hermann-pitton@arcor.de \
    --cc=arjan@infradead.org \
    --cc=barkalow@iabervon.org \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=video4linux-list@redhat.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;
as well as URLs for NNTP newsgroup(s).