From: Cong Wang <amwang@redhat.com>
To: Greg KH <gregkh@suse.de>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [Patch] debugfs: remove module_exit()
Date: Thu, 02 Dec 2010 12:15:49 +0800 [thread overview]
Message-ID: <4CF71D75.6070908@redhat.com> (raw)
In-Reply-To: <20101202035906.GA10006@suse.de>
On 12/02/10 11:59, Greg KH wrote:
>>> Even if they were (and hint, I don't think they are), they have nothing
>>> to do with the patch you created so they don't belong here. The rule is
>>> "one patch per logical change" and you didn't even describe that you
>>> were removing these lines in the changelog entry, so that's two strikes
>>> against removing these lines.
>>>
>>
>> Ok, teach me where DEBUG is used in that file?
>
> It is. And even if it isn't, it still shouldn't be done in this patch,
> which is my main point here.
>
I see.
>>>> Huh? Wasn't it a module before?
>>>
>>> Yes it was.
>>>
>>>> I think the problem is tracers use debugfs, it needs to depends on DEBUGFS=y.
>>>
>>> So if you disable tracing, then you could use debugfs as a module,
>>> right? So the patch should not be applied.
>>>
>>
>> No, that CONFIG is a bool, no way to make it as a module.
>> Since you insist, I will send a patch to make it as a module.
>
> {sigh} No, that's not what I ment at all.
>
Totally confused. :(
If you want to make it as a module, then we should not use 'bool'
and tracers should depend on =y.
If not, then this patch applies.
prev parent reply other threads:[~2010-12-02 4:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 9:19 Amerigo Wang
2010-12-01 1:35 ` Greg KH
2010-12-01 6:33 ` Cong Wang
2010-12-01 15:56 ` Greg KH
2010-12-02 3:17 ` Cong Wang
2010-12-02 3:59 ` Greg KH
2010-12-02 4:15 ` Cong Wang [this message]
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=4CF71D75.6070908@redhat.com \
--to=amwang@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--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
Powered by JetHome