From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: Re: [PATCH] drivers/hwtracing: make coresight-etm-perf.c explicitly non-modular
Date: Tue, 01 Mar 2016 02:56:21 +0000 [thread overview]
Message-ID: <20160301025620.GA17542@kroah.com> (raw)
In-Reply-To: <CANLsYkw7jVkE3KcuOz0w4ETGhRpGs_wzu6c+_MY+i0uzaXFhag@mail.gmail.com>
On Mon, Feb 29, 2016 at 09:10:06AM -0700, Mathieu Poirier wrote:
> On 27 February 2016 at 13:21, Paul Gortmaker
> <paul.gortmaker@windriver.com> wrote:
> > In commit 941943cf519f7cacbbcecee5c4ef4b77b466bd5c ("drivers/hwtracing:
> > make coresight-* explicitly non-modular") we removed all uses of
> > modular functions/macros in favour of their built-in equivlents in
> > this subsystem.
> >
> > However that commit and commit 0bcbf2e30ff2271b54f54c8697a185f7d86ec6e4
> > ("coresight: etm-perf: new PMU driver for ETM tracers") were in flight
> > at the same time, and hence one new non-modular user of module_init
> > crept back in. Fix it up like we did all the others.
> >
> > Since module_init translates to device_initcall in the non-modular
> > case, the init ordering remains unchanged with this commit.
> >
> > Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> > Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> > ---
> > drivers/hwtracing/coresight/coresight-etm-perf.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/hwtracing/coresight/coresight-etm-perf.c b/drivers/hwtracing/coresight/coresight-etm-perf.c
> > index 36153a77e982..755125f7917f 100644
> > --- a/drivers/hwtracing/coresight/coresight-etm-perf.c
> > +++ b/drivers/hwtracing/coresight/coresight-etm-perf.c
> > @@ -21,7 +21,7 @@
> > #include <linux/device.h>
> > #include <linux/list.h>
> > #include <linux/mm.h>
> > -#include <linux/module.h>
> > +#include <linux/init.h>
> > #include <linux/perf_event.h>
> > #include <linux/slab.h>
> > #include <linux/types.h>
> > @@ -390,4 +390,4 @@ static int __init etm_perf_init(void)
> >
> > return ret;
> > }
> > -module_init(etm_perf_init);
> > +device_initcall(etm_perf_init);
>
> Yes of course - Applied.
>
> Greg, given the triviality of the changes, can you still pick this up
> for the next merge window?
Yes, want me to take it directly, or do you have more patches to send
me?
thanks,
greg k-h
next prev parent reply other threads:[~2016-03-01 2:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 20:21 [PATCH] drivers/hwtracing: make coresight-etm-perf.c explicitly non-modular Paul Gortmaker
2016-02-29 16:10 ` Mathieu Poirier
2016-03-01 2:56 ` Greg Kroah-Hartman [this message]
2016-03-01 15:36 ` Mathieu Poirier
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=20160301025620.GA17542@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=paul.gortmaker@windriver.com \
/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