public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Jon Masters <jonathan@jonmasters.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Christoph Hellwig <hch@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: CONFIG_MARKERS
Date: Wed, 23 Jan 2008 12:11:39 -0500	[thread overview]
Message-ID: <20080123171139.GA22229@Krystal> (raw)
In-Reply-To: <1201106023.25284.58.camel@perihelion>

* Jon Masters (jonathan@jonmasters.org) wrote:
> On Wed, 2008-01-23 at 10:01 -0500, Mathieu Desnoyers wrote:
> 
> > if (!(mod->taints & (TAINT_FORCED_MODULE | TAINT_PROPRIETARY_MODULE)))
> > 
> > Which remembers me to never write code before my first coffee in the
> > morning ;)
> 
> I switched to decaf and joined a gym...for someone who used to have 23
> shots of espresso some days, it's a change.
> 

I only have two a day, in the morning and exercise regularly. But still,
coding with only one eye opened is not recommended. :)

> But more importantly, are you going to take care of patching this up, or
> shall I send something out? It's up to you.
> 

I would prefer to wait until we have some clear statement on this issue
before I submit a patch (allowing markers in proprietary modules or
not).

As soon as we have an answer, I'll cook the one-liner.

Mathieu

> Jon.
> 
> 

-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

  reply	other threads:[~2008-01-23 17:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 19:13 CONFIG_MARKERS Jon Masters
2008-01-23  3:00 ` CONFIG_MARKERS Frank Ch. Eigler
2008-01-23  3:10   ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-23  4:17     ` CONFIG_MARKERS Jon Masters
2008-01-23 13:14       ` CONFIG_MARKERS Frank Ch. Eigler
2008-01-23 14:48         ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-23 15:01           ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-23 16:33             ` CONFIG_MARKERS Jon Masters
2008-01-23 17:11               ` Mathieu Desnoyers [this message]
2008-01-24  5:25           ` CONFIG_MARKERS Valdis.Kletnieks
2008-01-24  6:19             ` CONFIG_MARKERS Jon Masters
2008-01-24 12:47               ` [PATCH] Linux Kernel Markers Support for Proprierary Modules Mathieu Desnoyers
2008-01-24 18:27                 ` Valdis.Kletnieks
2008-01-24 20:35                 ` Jon Masters
2008-01-25  1:27                 ` Rusty Russell
2008-01-25  7:56                 ` Jan Engelhardt
2008-01-25  8:03                   ` Valdis.Kletnieks
2008-01-25 16:32                     ` Alan Cox
2008-01-25 15:31                   ` Jon Masters
2008-01-25 16:01                     ` Jan Engelhardt
2008-01-26  3:27                     ` Rusty Russell
2008-01-26  4:21                       ` Jon Masters
2008-01-27 10:48                         ` Jan Engelhardt

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=20080123171139.GA22229@Krystal \
    --to=mathieu.desnoyers@polymtl.ca \
    --cc=akpm@linux-foundation.org \
    --cc=fche@redhat.com \
    --cc=hch@infradead.org \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@linux-foundation.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