From: Markus Elfring <Markus.Elfring@web.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>, kernel-janitors@vger.kernel.org
Cc: Enrico Weigelt <lkml@metux.net>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
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>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: drivers: Adjust scope for CONFIG_HAS_IOMEM before devm_platform_ioremap_resource()
Date: Mon, 24 Jun 2019 11:00:39 +0000 [thread overview]
Message-ID: <258fa411-43a7-14dc-95c2-6a3b336b3871@web.de> (raw)
In-Reply-To: <CAMRc=McepqowJNi6ay6x9KKoHOC8aCxP_ob12SgbsnJU_sKQng@mail.gmail.com>
> In its current form it makes the code even less readable.
This can be your development opinion.
> The #ifdef should actually be one line lower
I suggested that the conditional compilation can contain also a blank line
together with a comment block.
> and touch the comment instead of the EXPORT_SYMBOL() related to a different function.
I find that this macro call was kept unchanged.
Regards,
Markus
next prev parent reply other threads:[~2019-06-24 11:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190221162627.3476-1-brgl@bgdev.pl>
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
2019-06-24 10:05 ` Enrico Weigelt, metux IT consult
2019-06-24 10:46 ` Bartosz Golaszewski
2019-06-24 11:00 ` Markus Elfring [this message]
2019-06-24 18:22 ` 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=258fa411-43a7-14dc-95c2-6a3b336b3871@web.de \
--to=markus.elfring@web.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.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=lkml@metux.net \
--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).