mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Johnny Lever <johnny.lever@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] PCI-Express AER implemetation: AER core and aerdriver
Date: Wed, 12 Jul 2006 19:32:42 +0200	[thread overview]
Message-ID: <1152725562.3217.62.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <c770ab230607121021k550c3d2epf6acefa8fed491a1@mail.gmail.com>

On Wed, 2006-07-12 at 13:21 -0400, Johnny Lever wrote:
> >With Arjan's comments, I changed EXPORT_SYMBOL to EXPORT_SYMBOL_GPL.
> Sorry for flooding your emailbox again. :)
> 
> I think we should have "moron-proof" review system on LKML. Simplest
> way to get started is to ignore the EXPORT_SYMBOL_GPL "missionaries"
> trying to 'convert' code without giving proper thought to its
> implications or without ascertaining the correctness of the
> conversion.

I don't know where you get the "convert" idea from; this is new code and
new, linux specific API/functionality.

Some companies and people contribute a lot to the Linux kernel, all
under the GPL. In my opinion it is entirely fair that those companies
can expect that their efforts, which are new and Linux specific
functionality/APIs, will be used in compliance with the license and in a
level playing field. With "Level playing field" I mean that their
competitors ought to play by the same rules, eg comply with the letter
and spirit of the GPL. These companies make a sacrifice by giving their
code up under the GPL rather than charging for it proprietary, and they
do so gladly (and for their internal reasons). Demanding that these
companies then also allow that same code to be used by other companies
who do not give anything back to Linux... is just really bad for Linux
both in the short and the long term.

> Dimwits.

good thing you're using a fake gmail account instead of your own name,
it means it's just a very obvious troll attempt....


  reply	other threads:[~2006-07-12 17:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12 17:21 Johnny Lever
2006-07-12 17:32 ` Arjan van de Ven [this message]
2006-07-12 18:07   ` Johnny Lever
2006-07-13  8:45     ` Christoph Hellwig
2006-07-13 11:26       ` Johnny Lever
  -- strict thread matches above, loose matches on Subject: below --
2006-07-31  3:00 [PATCH 1/5] PCI-Express AER implemetation: aer howto document Zhang, Yanmin
2006-07-31  3:10 ` [PATCH 2/5] PCI-Express AER implemetation: Add new defines to pci_regs.h Zhang, Yanmin
2006-07-31  3:14   ` [PATCH 3/5] PCI-Express AER implemetation: export pcie_port_bus_type Zhang, Yanmin
2006-07-31  3:22     ` [PATCH 4/5] PCI-Express AER implemetation: AER core and aerdriver Zhang, Yanmin
2006-07-12  7:10 [PATCH 1/5] PCI-Express AER implemetation: aer howto document Zhang, Yanmin
2006-07-12  7:16 ` [PATCH 2/5] PCI-Express AER implemetation: Add new defines to pci_regs.h Zhang, Yanmin
2006-07-12  7:22   ` [PATCH 3/5] PCI-Express AER implemetation: export pcie_port_bus_type Zhang, Yanmin
2006-07-12  7:32     ` [PATCH 4/5] PCI-Express AER implemetation: AER core and aerdriver Zhang, Yanmin
2006-07-12  8:06       ` Zhang, Yanmin
2006-07-12 13:16         ` Arjan van de Ven
2006-07-13  2:08           ` Zhang, Yanmin
2006-07-12 16:26         ` Andi Kleen
2006-07-13  2:16           ` Zhang, Yanmin
2006-07-14  5:25 ` [PATCH 1/5] PCI-Express AER implemetation: aer howto document Zhang, Yanmin
2006-07-14  5:27   ` [PATCH 2/5] PCI-Express AER implemetation: Add new defines to pci_regs.h Zhang, Yanmin
2006-07-14  5:28     ` [PATCH 3/5] PCI-Express AER implemetation: export pcie_port_bus_type Zhang, Yanmin
2006-07-14  5:30       ` [PATCH 4/5] PCI-Express AER implemetation: AER core and aerdriver Zhang, Yanmin

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=1152725562.3217.62.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=johnny.lever@gmail.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®