From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arc: do not export symbols in troubleshoot.c
Date: Thu, 19 Feb 2015 16:21:21 +0530 [thread overview]
Message-ID: <54E5C029.5000900@synopsys.com> (raw)
In-Reply-To: <1424287233.2046.113.camel@stgolabs.net>
On Thursday 19 February 2015 12:50 AM, Davidlohr Bueso wrote:
> On Wed, 2015-02-18 at 11:13 -0800, Davidlohr Bueso wrote:
>> > print_task_path_n_nm() is local to this file, its only
>> > user being show_regs(). Mark the function static and avoid
>> > the EXPORT_SYMBOL.
>> >
>> > Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
>> > ---
>> >
>> > Compile tested only.
> What am I saying! not tested. Got confused with another patch :)
>
And I got excited that core kernel developers are now starting to compile for ARC
:-) I'm sure we will get there.
Thx for the patch David.
Acked-by: Vineet Gupta <vgupta@synoipsys.com>
-Vineet
prev parent reply other threads:[~2015-02-19 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 19:13 [PATCH] arc: do not export symbols in troubleshoot.c Davidlohr Bueso
2015-02-18 19:20 ` Davidlohr Bueso
2015-02-19 10:51 ` Vineet Gupta [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=54E5C029.5000900@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--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