From: Ingo Molnar <mingo@elte.hu>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git-pull -tip] x86:perf_counter cleanup
Date: Sun, 8 Mar 2009 11:41:33 +0100 [thread overview]
Message-ID: <20090308104133.GA3360@elte.hu> (raw)
In-Reply-To: <1236508753.3638.3.camel@localhost.localdomain>
* Jaswinder Singh Rajput <jaswinder@kernel.org> wrote:
> Hello Peter,
>
> On Sun, 2009-03-08 at 11:20 +0100, Peter Zijlstra wrote:
> > On Sun, 2009-03-08 at 15:43 +0530, Jaswinder Singh Rajput wrote:
> >
> > > +/*
> > > + * Exported because of ACPI idle
> > > + */
> > > u64 hw_perf_save_disable(void)
> > > {
> > > if (unlikely(!perf_counters_initialized))
> > > @@ -270,9 +272,6 @@ u64 hw_perf_save_disable(void)
> > >
> > > return pmc_ops->save_disable_all();
> > > }
> > > -/*
> > > - * Exported because of ACPI idle
> > > - */
> > > EXPORT_SYMBOL_GPL(hw_perf_save_disable);
> > >
> > > static void pmc_intel_restore_all(u64 ctrl)
> > > @@ -301,6 +300,9 @@ static void pmc_amd_restore_all(u64 ctrl)
> > > }
> > > }
> > >
> > > +/*
> > > + * Exported because of ACPI idle
> > > + */
> > > void hw_perf_restore(u64 ctrl)
> > > {
> > > if (unlikely(!perf_counters_initialized))
> > > @@ -308,9 +310,6 @@ void hw_perf_restore(u64 ctrl)
> > >
> > > pmc_ops->restore_all(ctrl);
> > > }
> > > -/*
> > > - * Exported because of ACPI idle
> > > - */
> > > EXPORT_SYMBOL_GPL(hw_perf_restore);
> >
> > Please leave those comments where they are, they do not describe the
> > function, but comment on the export.
>
> Have you checked this:
> http://git.kernel.org/?p=linux/kernel/git/jaswinder/linux-2.6-tip.git;a=commitdiff;h=1ae843834668af3a30484e256fb27dc1a49f59cb
>
> These leads to warnings:
> WARNING: EXPORT_SYMBOL(foo); should immediately follow its function/variable
> WARNING: EXPORT_SYMBOL(foo); should immediately follow its function/variable
ignore those checkpatch warnings, they are wrong in this case.
> So we have two options:
> 1. which I already shown above
> 2. remove these comments
3. ignore incorrect warnings
Ingo
next prev parent reply other threads:[~2009-03-08 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 10:13 [git-pull -tip] x86:perf_counter cleanup Jaswinder Singh Rajput
2009-03-08 10:20 ` Peter Zijlstra
2009-03-08 10:39 ` Jaswinder Singh Rajput
2009-03-08 10:41 ` Ingo Molnar [this message]
2009-03-08 11:39 ` Jaswinder Singh Rajput
2009-03-08 10:46 ` Peter Zijlstra
2009-03-08 10:32 ` Peter Zijlstra
2009-03-08 10:34 ` Peter Zijlstra
2009-03-08 15:52 ` [tip:perfcounters/core] x86: perf_counter cleanup Peter Zijlstra
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=20090308104133.GA3360@elte.hu \
--to=mingo@elte.hu \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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 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.