From: Greg KH <gregkh@linuxfoundation.org>
To: Akhilesh Kumar <akhilesh.lxr@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Debug ] fs : export debugfs_file_operations symbol
Date: Fri, 3 Aug 2012 15:10:31 -0700 [thread overview]
Message-ID: <20120803221031.GA4925@kroah.com> (raw)
In-Reply-To: <CADArhcAJzp-t0EaEuqjXP-w85MjPLXTXfhAYtCdue9drtt=HMw@mail.gmail.com>
On Sat, Aug 04, 2012 at 03:30:44AM +0530, Akhilesh Kumar wrote:
> Hi Hartman
>
> This patch just exports debugfs_file_operations which improve debugfs
> interface .
> Please review below patch for main line and share your review comments.
>
> Thanks,
> Akhilesh
>
>
>
>
> From fd68900cd32f220beee70b55c20b3c74a38d7df8 Mon Sep 17 00:00:00 2001
> From: Akhilesh Kumar <akhilesh.lxr@gmail.com>
> Date: Tue, 31 Jul 2012 17:17:12 +0530
> Subject:[Debug ] fs : export debugfs_file_operations symbol
>
> debugfs_file_operations is usefull for file system
> debugging debugfs_file_operations is not an exported
> symbol.
>
> Any kernel module (http://lwn.net/Articles/371208/) using
>
> debugfs_file_operations will result in build failures
> because of this.
>
> This patch just exports debugfs_file_operations to fix such problems in
> future
>
> Signed-off-by: Akhilesh Kumar <akhilesh.lxr@gmail.com>
> ---
> fs/debugfs/file.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/fs/debugfs/file.c b/fs/debugfs/file.c
> index 2340f69..a5150d8 100644
> --- a/fs/debugfs/file.c
> +++ b/fs/debugfs/file.c
> @@ -40,6 +40,7 @@ const struct file_operations debugfs_file_operations = {
> .open = simple_open,
> .llseek = noop_llseek,
> };
> +EXPORT_SYMBOL(debugfs_file_operations);
I fail to understand how this will help you out at all. You should not
be using this symbol, why would you?
Please show the in-kernel code that needs it, and I will be glad to
reconsider this patch, after it it fixed to use EXPORT_SYMBOL_GPL() as
well, to be consistant with the other debugfs symbols.
greg k-h
parent reply other threads:[~2012-08-03 22:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CADArhcAJzp-t0EaEuqjXP-w85MjPLXTXfhAYtCdue9drtt=HMw@mail.gmail.com>]
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=20120803221031.GA4925@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akhilesh.lxr@gmail.com \
--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