From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/4] coresight: allow to build as modules
Date: Thu, 17 May 2018 09:06:43 +0200 [thread overview]
Message-ID: <20180517070643.GC13919@kroah.com> (raw)
In-Reply-To: <20180516143322.0eaecaa72f8a65f19fd7dabf@arm.com>
On Wed, May 16, 2018 at 02:33:22PM -0500, Kim Phillips wrote:
> Allow to build coresight as modules. This greatly enhances developer
> efficiency by allowing the development to take place exclusively on the
> target, and without needing to reboot in between changes.
>
> - Kconfig bools become tristates, to allow =m
>
> - MODULE_* macros added: Please correct me if I'm wrong:
> - assume LICENSE is "GPL v2"
> - tried to get as close to original authors for MODULE_AUTHOR
>
> - The 'select' Kconfig statements are replaced with 'depends on'
> clauses, to specify the dependencies between the modules including
> other fixes, e.g., coresight-stm unconditionally calls
> stm_register_device, it therefore depends on STM.
>
> - use -objs to denote merge object directives in Makefile, adds a
> coresight-core nomenclature for the base module.
>
> - add a coresight_exit() that unregisters the coresight bus, add remove
> fns for most others.
>
> - fix up modules with ID tables for autoloading on boot, add missing
> __exit attributes
>
> - move coresight_vpid_to_pid to an externed, single instance in
> coresight-core, to be used by all submodules.
That's a ton of different things to be doing all at once in this patch.
Please break it up into logical steps (like you describe here!) which
will make it much easier and trivial to review.
As it is, I'm not even going to look at the mess-of-a-diff that I
imagine the above results in :)
thanks,
greg k-h
next prev parent reply other threads:[~2018-05-17 7:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 19:06 [PATCH 3/4] coresight: allow to build as modules Kim Phillips
2018-05-08 19:31 ` Randy Dunlap
2018-05-08 20:37 ` Kim Phillips
2018-05-09 6:01 ` Randy Dunlap
2018-05-16 19:33 ` [PATCH v2 " Kim Phillips
2018-05-17 7:06 ` Greg Kroah-Hartman [this message]
2018-05-18 1:20 ` [PATCH 1/6] coresight: remove CORESIGHT_LINKS_AND_SINKS dependencies and selections Kim Phillips
2018-05-18 1:20 ` [PATCH 2/6] coresight: fix CORESIGHT_STM -- STM dependency Kim Phillips
2018-05-18 1:20 ` [PATCH 3/6] coresight: use IS_ENABLED for CONFIGs that may be modules Kim Phillips
2018-05-18 1:20 ` [PATCH 4/6] coresight: move shared barrier_pkt[] to coresight_priv.h Kim Phillips
2018-05-18 1:20 ` [PATCH 5/6] coresight: populate MODULE_AUTHOR, DESCRIPTION, and LICENSEs Kim Phillips
2018-05-22 17:53 ` Mathieu Poirier
2018-05-18 1:20 ` [PATCH 6/6] coresight: allow to build as modules Kim Phillips
2018-05-22 21:39 ` Mathieu Poirier
2018-05-24 23:49 ` Kim Phillips
2018-05-25 17:21 ` Mathieu Poirier
2018-05-25 17:12 ` Suzuki K Poulose
2018-05-25 17:27 ` Mathieu Poirier
2018-05-22 17:31 ` [PATCH 1/6] coresight: remove CORESIGHT_LINKS_AND_SINKS dependencies and selections Mathieu Poirier
2018-05-23 19:51 ` Kim Phillips
2018-05-24 15:32 ` Mathieu Poirier
2018-05-24 23:30 ` Kim Phillips
2018-05-25 15:27 ` Mathieu Poirier
2018-05-25 18:52 ` Kim Phillips
2018-05-25 19:09 ` 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=20180517070643.GC13919@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).