All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Greg KH <greg@kroah.com>
Cc: Jason Baron <jbaron@redhat.com>,
	yehuda@hq.newdream.net, LKML <linux-kernel@vger.kernel.org>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Dynamic Debug: Introduce global fake module param module.ddebug
Date: Thu, 5 Aug 2010 22:11:18 +0200	[thread overview]
Message-ID: <201008052211.18666.trenn@suse.de> (raw)
In-Reply-To: <20100805172554.GA12234@kroah.com>

On Thursday 05 August 2010 07:25:54 pm Greg KH wrote:
> On Thu, Aug 05, 2010 at 06:05:40PM +0200, Thomas Renninger wrote:
> > On Thursday 05 August 2010 17:39:10 Jason Baron wrote:
...
> > So, I have your acked-by for this one?
> > Let's get this pushed into a tree, with some luck it still could make it
> > into 2.6.36? The other three have been taken by Pekka? He said something
> > about taking them, but I haven't received any confirmation.
> > Ah no, he acked-by them only.
>
> It's too late for .36 as none of this has been tested in linux-next yet.
> How about for .37?
No problem. I send you a clean patchset tomorrow.
I have one additional idea I'll try to build in:
Complain if a module uses ddebug as module parameter at module
insertion time that this is a reserved keyword/param that must not be used.

I'll leave out lkml, Andrew and Pekka (I thought they could queue these).

Thanks everybody,

     Thomas

  reply	other threads:[~2010-08-05 20:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 12:14 [PATCH] Dynamic Debug: Introduce global fake module param module.ddebug Thomas Renninger
2010-07-26 13:42 ` Thomas Renninger
2010-08-05 15:39 ` Jason Baron
2010-08-05 16:05   ` Thomas Renninger
2010-08-05 17:25     ` Greg KH
2010-08-05 20:11       ` Thomas Renninger [this message]
2010-08-05 17:26     ` Jason Baron
2010-08-05 17:59       ` Greg KH

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=201008052211.18666.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=yehuda@hq.newdream.net \
    /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.