mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: caglar@pardus.org.tr
Cc: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	RT <linux-rt-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.24-rc7-rt2
Date: Tue, 15 Jan 2008 22:50:17 -0500	[thread overview]
Message-ID: <24149.1200455417@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 15 Jan 2008 02:37:37 +0200." <200801150237.44029.caglar@pardus.org.tr>

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

On Tue, 15 Jan 2008 02:37:37 +0200, =?utf-8?q?S=2E=C3=87a=C4=9Flar?= Onur said:
> And because of mcount-add-basic-support-for-gcc-profiler-instrum.patch, closed
> source nvidia-new module cannot be used with this release (mcount is exported
> GPL only), i know this is not supported but i used it with that [2] patch up
> until now without a single problem.

Playing devil's advocate here - the claim is that EXPORT_SYMBOL_GPL is to
indicate that code is getting too chummy with Linux internals.

However, in *this* case, isn't it "code that is too chummy with *GCC* internals",
and thus it isn't our place to say what can and can't be done with code that
is derivative of the GCC compiler? ;)

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2008-01-16  3:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 18:41 2.6.24-rc7-rt2 Steven Rostedt
2008-01-14 20:02 ` 2.6.24-rc7-rt2 Mark Knecht
2008-01-14 22:16 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-14 22:30   ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15 17:10     ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-17  2:07       ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-17 17:11         ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-17 17:25           ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-17 17:57             ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-15  0:37 ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-16  3:50   ` Valdis.Kletnieks [this message]
2008-01-16  4:04     ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16  6:23       ` 2.6.24-rc7-rt2 Valdis.Kletnieks
2008-01-16 14:12         ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16 16:22           ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-21 11:31             ` 2.6.24-rc7-rt2 Esben Nielsen
2008-01-21 12:49               ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-27 21:51                 ` 2.6.24-rc7-rt2 Esben Nielsen
2008-01-28  2:32               ` 2.6.24-rc7-rt2 Stefan Monnier
2008-01-16 13:17     ` 2.6.24-rc7-rt2 Alan Cox
2008-01-16  4:01   ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16  7:12     ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-16 10:11       ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-17  2:20         ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15  3:44 ` 2.6.24-rc7-rt2: WARNING: at include/linux/rcupreempt.h:110 rcu_enter_nohz() Mike Galbraith
2008-01-15 16:27 ` 2.6.24-rc7-rt2 Luotao Fu
2008-01-15 18:06   ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15 20:04     ` 2.6.24-rc7-rt2 Luotao Fu
2008-01-16 12:03     ` 2.6.24-rc7-rt2 [PATCH] latency tracer fix for ppc32 Luotao Fu
2008-01-17  3:26       ` Steven Rostedt

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=24149.1200455417@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=caglar@pardus.org.tr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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®