From: Markus Elfring <Markus.Elfring@web.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jack Ping CHNG <jack.ping.chng@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Himanshu Jha <himanshujha199640@gmail.com>
Cc: kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Enrico Weigelt <lkml@metux.net>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: drivers: Provide devm_platform_ioremap_resource_byname()
Date: Fri, 14 Jun 2019 18:14:33 +0200 [thread overview]
Message-ID: <48877575-90b9-3db5-7a25-53cf3817b2ee@web.de> (raw)
In-Reply-To: <20190614144706.GO9224@smile.fi.intel.com>
>> I don't like adding new apis with no user.
>
> Perhaps Jack Ping will send it as a first patch of his series where he utilizes
> this functionality. Would it be acceptable?
The proposed function can get wider application in a reasonable time frame
if a corresponding script for the semantic patch language (Coccinelle software)
would perform an automatic source code conversion (for example)
according to your change acceptance.
How do you think about to support a bit more collateral software evolution?
Regards,
Markus
next prev parent reply other threads:[~2019-06-14 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 13:26 [PATCH] " Markus Elfring
2019-06-14 13:38 ` Andy Shevchenko
2019-06-14 14:10 ` Greg Kroah-Hartman
2019-06-14 14:47 ` Andy Shevchenko
2019-06-14 15:32 ` Greg Kroah-Hartman
2019-06-14 16:14 ` Markus Elfring [this message]
2019-06-15 8:44 ` Julia Lawall
2019-06-15 10:23 ` Markus Elfring
2019-06-17 9:55 ` [PATCH] " Rafael J. Wysocki
2019-06-17 13:54 ` 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=48877575-90b9-3db5-7a25-53cf3817b2ee@web.de \
--to=markus.elfring@web.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=himanshujha199640@gmail.com \
--cc=jack.ping.chng@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linus.walleij@linaro.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
all inboxes | Powered by JetHome®