From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Keerthy <j-keerthy@ti.com>,
Linus Walleij <linus.walleij@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-gpio <linux-gpio@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers: Adjust scope for CONFIG_HAS_IOMEM before devm_platform_ioremap_resource()
Date: Mon, 24 Jun 2019 10:29:35 +0200 [thread overview]
Message-ID: <CAMpxmJX-wXQ-ff1RWkPmJBWSsP_v2MjZrA3fhj3HQX0_zM0eZA@mail.gmail.com> (raw)
In-Reply-To: <9efcbce2-4d49-7197-a3d8-0e83850892d5@web.de>
pt., 14 cze 2019 o 18:50 Markus Elfring <Markus.Elfring@web.de> napisał(a):
>
> From: Markus Elfring <elfring@users.sourceforge.net>
> Date: Fri, 14 Jun 2019 17:45:13 +0200
>
> Move the preprocessor statement “#ifdef CONFIG_HAS_IOMEM” so that
> the corresponding scope for conditional compilation includes also comments
> for this function implementation.
>
> Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
> ---
> drivers/base/platform.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/base/platform.c b/drivers/base/platform.c
> index 4d1729853d1a..a5f40974a6ef 100644
> --- a/drivers/base/platform.c
> +++ b/drivers/base/platform.c
> @@ -78,6 +78,7 @@ struct resource *platform_get_resource(struct platform_device *dev,
> return NULL;
> }
> EXPORT_SYMBOL_GPL(platform_get_resource);
> +#ifdef CONFIG_HAS_IOMEM
>
> /**
> * devm_platform_ioremap_resource - call devm_ioremap_resource() for a platform
> @@ -87,7 +88,6 @@ EXPORT_SYMBOL_GPL(platform_get_resource);
> * resource management
> * @index: resource index
> */
> -#ifdef CONFIG_HAS_IOMEM
> void __iomem *devm_platform_ioremap_resource(struct platform_device *pdev,
> unsigned int index)
> {
> --
> 2.22.0
>
And what is the purpose of that?
Bart
next prev parent reply other threads:[~2019-06-24 8:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 16:26 [PATCH] drivers: depend on HAS_IOMEM for devm_platform_ioremap_resource() Bartosz Golaszewski
2019-02-21 16:47 ` Greg Kroah-Hartman
2019-02-21 19:55 ` Andy Shevchenko
2019-02-21 19:56 ` Andy Shevchenko
2019-02-22 9:04 ` Bartosz Golaszewski
2019-02-22 10:24 ` Andy Shevchenko
2019-02-22 14:22 ` Rob Herring
2019-02-22 16:22 ` Linus Walleij
2019-06-14 16:50 ` [PATCH] drivers: Adjust scope for CONFIG_HAS_IOMEM before devm_platform_ioremap_resource() Markus Elfring
2019-06-24 8:29 ` Bartosz Golaszewski [this message]
2019-06-24 10:05 ` Enrico Weigelt, metux IT consult
2019-06-24 10:46 ` Bartosz Golaszewski
2019-06-24 11:00 ` Markus Elfring
2019-06-24 18:22 ` [PATCH] " Enrico Weigelt, metux IT consult
2019-06-25 7:10 ` Bartosz Golaszewski
2019-06-25 7:30 ` Greg Kroah-Hartman
2019-06-25 7:32 ` Bartosz Golaszewski
2019-06-25 7:51 ` Markus Elfring
2019-06-25 7:42 ` Markus Elfring
2019-06-24 10:51 ` [PATCH] " Markus Elfring
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=CAMpxmJX-wXQ-ff1RWkPmJBWSsP_v2MjZrA3fhj3HQX0_zM0eZA@mail.gmail.com \
--to=bgolaszewski@baylibre.com \
--cc=Markus.Elfring@web.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=gregkh@linuxfoundation.org \
--cc=j-keerthy@ti.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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 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).