From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, linux-acpi@vger.kernel.org
Subject: [PATCH v1 2/2] resource: Convert DEFINE_RES_NAMED() to be compound literal
Date: Wed, 9 Nov 2022 12:51:14 +0200 [thread overview]
Message-ID: <20221109105114.32886-2-andriy.shevchenko@linux.intel.com> (raw)
In-Reply-To: <20221109105114.32886-1-andriy.shevchenko@linux.intel.com>
Currently DEFINE_RES_NAMED() can only be used to fill the static data.
In some cases it would be convenient to use it as right value in the
assignment operation. But it can't be done as is, because compiler has
no clue about the data layout. Converting it to be a compound literal
allows the above mentioned usage.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
include/linux/ioport.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/ioport.h b/include/linux/ioport.h
index 27642ca15d93..67d3fb2133b6 100644
--- a/include/linux/ioport.h
+++ b/include/linux/ioport.h
@@ -155,7 +155,7 @@ enum {
/* helpers to define resources */
#define DEFINE_RES_NAMED(_start, _size, _name, _flags) \
- { \
+(struct resource) { \
.start = (_start), \
.end = (_start) + (_size) - 1, \
.name = (_name), \
--
2.35.1
next prev parent reply other threads:[~2022-11-09 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 10:51 [PATCH v1 1/2] resource: Replace printk(KERN_WARNING) by pr_warn() Andy Shevchenko
2022-11-09 10:51 ` Andy Shevchenko [this message]
2022-11-09 11:14 ` [PATCH v1 2/2] resource: Convert DEFINE_RES_NAMED() to be compound literal Rafael J. Wysocki
2022-11-09 11:12 ` [PATCH v1 1/2] resource: Replace printk(KERN_WARNING) by pr_warn() Rafael J. Wysocki
2022-11-09 11:26 ` Andy Shevchenko
2022-11-09 13:37 ` Greg Kroah-Hartman
2022-11-09 15:56 ` Andy Shevchenko
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=20221109105114.32886-2-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-acpi@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