From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
John Garry <john.garry@huawei.com>, Wei Xu <xuwei5@hisilicon.com>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
Zhichang Yuan <yuanzhichang@hisilicon.com>
Subject: [resend, PATCH v1 1/1] logic_pio: Use RESOURCE_SIZE_MAX definition
Date: Fri, 2 Feb 2024 17:45:59 +0200 [thread overview]
Message-ID: <20240202154744.473467-1-andriy.shevchenko@linux.intel.com> (raw)
Use a predefined limit instead of hardcoding it.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
v1: resent with the main contributrs in the Cc list
Initial contribution was here more than a few months ago:
https://lore.kernel.org/r/20230911224500.16677-1-andriy.shevchenko@linux.intel.com
followed by
20231016132611.1201402-1-andriy.shevchenko@linux.intel.com
lib/logic_pio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/logic_pio.c b/lib/logic_pio.c
index 2ea564a40064..1cab23e4f856 100644
--- a/lib/logic_pio.c
+++ b/lib/logic_pio.c
@@ -175,7 +175,7 @@ resource_size_t logic_pio_to_hwaddr(unsigned long pio)
if (range)
return range->hw_start + pio - range->io_start;
- return (resource_size_t)~0;
+ return RESOURCE_SIZE_MAX;
}
/**
--
2.43.0.rc1.1.gbec44491f096
next reply other threads:[~2024-02-03 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 15:45 Andy Shevchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-26 17:23 [resend, PATCH v1 1/1] logic_pio: Use RESOURCE_SIZE_MAX definition Andy Shevchenko
2023-10-16 13:26 Andy Shevchenko
2023-11-20 17:19 ` Andy Shevchenko
2023-12-22 15:03 ` Andy Shevchenko
2023-12-22 16:11 ` Matthew Wilcox
2024-02-02 15:35 ` Andy Shevchenko
2024-02-02 22:37 ` Matthew Wilcox
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=20240202154744.473467-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=gabriele.paoloni@huawei.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.org \
--cc=xuwei5@hisilicon.com \
--cc=yuanzhichang@hisilicon.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: 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