From: Mathieu Poirier <mathieu.poirier@linaro.org> To: Arnd Bergmann <arnd@arndb.de> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>, Suzuki K Poulose <suzuki.poulose@arm.com>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: [PATCH] coresight: platform: add OF/APCI dependency Date: Mon, 17 Jun 2019 13:40:14 -0600 [thread overview] Message-ID: <CANLsYkyraS+1QACrSVMak=CUxtupHcW6=5dODNn3SeyUvqhsMw@mail.gmail.com> (raw) In-Reply-To: <20190617125908.1674177-1-arnd@arndb.de> On Mon, 17 Jun 2019 at 06:59, Arnd Bergmann <arnd@arndb.de> wrote: > > When neither CONFIG_OF nor CONFIG_ACPI are set, we get a harmless > build warning: > > drivers/hwtracing/coresight/coresight-platform.c:26:12: error: unused function 'coresight_alloc_conns' > [-Werror,-Wunused-function] > static int coresight_alloc_conns(struct device *dev, > ^ > drivers/hwtracing/coresight/coresight-platform.c:46:1: error: unused function 'coresight_find_device_by_fwnode' > [-Werror,-Wunused-function] > coresight_find_device_by_fwnode(struct fwnode_handle *fwnode) > > As the code is useless in that configuration anyway, just add > a Kconfig dependency that only allows building when at least > one of the two is set. > > This should not hinder compile-testing, as CONFIG_OF can be > enabled on any architecture. > > Fixes: ac0e232c12f0 ("coresight: platform: Use fwnode handle for device search") > Signed-off-by: Arnd Bergmann <arnd@arndb.de> > --- > drivers/hwtracing/coresight/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/hwtracing/coresight/Kconfig b/drivers/hwtracing/coresight/Kconfig > index 5487d4a1abc2..14638db4991d 100644 > --- a/drivers/hwtracing/coresight/Kconfig > +++ b/drivers/hwtracing/coresight/Kconfig > @@ -4,6 +4,7 @@ > # > menuconfig CORESIGHT > bool "CoreSight Tracing Support" > + depends on OF || ACPI I have applied this - thanks, Mathieu > select ARM_AMBA > select PERF_EVENTS > help > -- > 2.20.0 >
WARNING: multiple messages have this Message-ID (diff)
From: Mathieu Poirier <mathieu.poirier@linaro.org> To: Arnd Bergmann <arnd@arndb.de> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, linux-arm-kernel <linux-arm-kernel@lists.infradead.org>, Suzuki K Poulose <suzuki.poulose@arm.com> Subject: Re: [PATCH] coresight: platform: add OF/APCI dependency Date: Mon, 17 Jun 2019 13:40:14 -0600 [thread overview] Message-ID: <CANLsYkyraS+1QACrSVMak=CUxtupHcW6=5dODNn3SeyUvqhsMw@mail.gmail.com> (raw) In-Reply-To: <20190617125908.1674177-1-arnd@arndb.de> On Mon, 17 Jun 2019 at 06:59, Arnd Bergmann <arnd@arndb.de> wrote: > > When neither CONFIG_OF nor CONFIG_ACPI are set, we get a harmless > build warning: > > drivers/hwtracing/coresight/coresight-platform.c:26:12: error: unused function 'coresight_alloc_conns' > [-Werror,-Wunused-function] > static int coresight_alloc_conns(struct device *dev, > ^ > drivers/hwtracing/coresight/coresight-platform.c:46:1: error: unused function 'coresight_find_device_by_fwnode' > [-Werror,-Wunused-function] > coresight_find_device_by_fwnode(struct fwnode_handle *fwnode) > > As the code is useless in that configuration anyway, just add > a Kconfig dependency that only allows building when at least > one of the two is set. > > This should not hinder compile-testing, as CONFIG_OF can be > enabled on any architecture. > > Fixes: ac0e232c12f0 ("coresight: platform: Use fwnode handle for device search") > Signed-off-by: Arnd Bergmann <arnd@arndb.de> > --- > drivers/hwtracing/coresight/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/hwtracing/coresight/Kconfig b/drivers/hwtracing/coresight/Kconfig > index 5487d4a1abc2..14638db4991d 100644 > --- a/drivers/hwtracing/coresight/Kconfig > +++ b/drivers/hwtracing/coresight/Kconfig > @@ -4,6 +4,7 @@ > # > menuconfig CORESIGHT > bool "CoreSight Tracing Support" > + depends on OF || ACPI I have applied this - thanks, Mathieu > select ARM_AMBA > select PERF_EVENTS > help > -- > 2.20.0 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-17 19:40 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-17 12:58 [PATCH] coresight: platform: add OF/APCI dependency Arnd Bergmann 2019-06-17 12:58 ` Arnd Bergmann 2019-06-17 13:19 ` Suzuki K Poulose 2019-06-17 13:19 ` Suzuki K Poulose 2019-06-17 19:40 ` Mathieu Poirier [this message] 2019-06-17 19:40 ` 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='CANLsYkyraS+1QACrSVMak=CUxtupHcW6=5dODNn3SeyUvqhsMw@mail.gmail.com' \ --to=mathieu.poirier@linaro.org \ --cc=alexander.shishkin@linux.intel.com \ --cc=arnd@arndb.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=suzuki.poulose@arm.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: linkBe 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.