From: Andrew Morton <akpm@linux-foundation.org>
To: Jason Baron <jbaron@redhat.com>
Cc: Thomas Renninger <trenn@suse.de>,
Andi Kleen <andi@firstfloor.org>,
LKML <linux-kernel@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: Dynamic Debug broken on 2.6.35-rc3?
Date: Thu, 8 Jul 2010 14:53:00 -0700 [thread overview]
Message-ID: <20100708145300.d36cf006.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100708213927.GB2934@redhat.com>
On Thu, 8 Jul 2010 17:39:28 -0400
Jason Baron <jbaron@redhat.com> wrote:
> Make sure we properly call ddebug_remove_module() when a module fails to
> load. In addition, pass the pointer to the "debug table", to both
> ddebug_add_module(), and ddebug_remove_module() so that we can uniquely
> identify each set of debug statements. In this way even modules with the
> same name can be properly identified and removed.
>
>
> Signed-off-by: Jason Baron <jbaron@redhat.com>
It'd be nice to track the Reported-by:s. And the Tested-by:s if/when
they arrive. SighIllDoIt.
The patch (almost) applies to 2.6.34. So are we missing a Cc:stable tag
as well?
Also, this patch's title is now "Re: Dynamic Debug broken on
2.6.35-rc3?" which isn't very good. I can invent a new title for it,
but that means we don't have a well-understood handle to refer to this
patch, and to perform searches with, etc.
Maybe a resend would be best..
next prev parent reply other threads:[~2010-07-08 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 15:44 Dynamic Debug broken on 2.6.35-rc3? Thomas Renninger
2010-07-01 16:26 ` Jason Baron
2010-07-02 16:55 ` Thomas Renninger
2010-07-08 21:39 ` Jason Baron
2010-07-08 21:53 ` Andrew Morton [this message]
2010-07-09 11:03 ` Thomas Renninger
2010-07-09 13:30 ` Jason Baron
2010-07-12 14:24 ` Thomas Renninger
2010-07-12 16:21 ` Jason Baron
2010-07-12 21:21 ` Yehuda Sadeh
2010-07-12 21:47 ` Andi Kleen
2010-07-13 20:38 ` Yehuda Sadeh
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=20100708145300.d36cf006.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hare@suse.de \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.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 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.