On Thu, 2015-04-30 at 22:53 +0200, Paul Bolle wrote: > On Wed, 2015-04-29 at 15:19 +0300, Ivan T. Ivanov wrote: > > > +config CORESIGHT_QCOM_REPLICATOR > > + bool "Qualcomm CoreSight Replicator driver" > > + help > > + This enables support for CoreSight link and sink > > driver that are > > + responsible for transporting and collecting the > > trace data > > + respectively. Link and sinks are dynamically > > aggregated with a trace > > + entity at run time to form a complete trace path. > > > --- a/drivers/hwtracing/coresight/Makefile > > +++ b/drivers/hwtracing/coresight/Makefile > > > +obj-$(CONFIG_CORESIGHT_QCOM_REPLICATOR) += coresight-replicator-qcom.o > > CORESIGHT_QCOM_REPLICATOR is a bool symbol. So > coresight-replicator-qcom.o will never be part of a module. >
Thank you. I am going to fallow approach taken by Mathieu in [1]. Is this OK with you? Regards, Ivan [1] https://lkml.org/lkml/2015/5/6/524 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
