From: Jean Delvare <khali@linux-fr.org>
To: linux-acpi@vger.kernel.org
Cc: Len Brown <lenb@kernel.org>
Subject: [PATCH] acpi_check_resource_conflict doesn't change the resource
Date: Wed, 11 Nov 2009 15:22:15 +0100 [thread overview]
Message-ID: <20091111152215.66617c8f@hyperion.delvare> (raw)
The acpi_check_resource_conflict function doesn't change the resource
it operates on, so the res parameter can be marked const.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Cc: Len Brown <lenb@kernel.org>
---
drivers/acpi/osl.c | 2 +-
include/linux/acpi.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--- linux-2.6.32-rc6.orig/drivers/acpi/osl.c 2009-09-28 10:28:34.000000000 +0200
+++ linux-2.6.32-rc6/drivers/acpi/osl.c 2009-11-11 15:13:30.000000000 +0100
@@ -1118,7 +1118,7 @@ __setup("acpi_enforce_resources=", acpi_
/* Check for resource conflicts between ACPI OperationRegions and native
* drivers */
-int acpi_check_resource_conflict(struct resource *res)
+int acpi_check_resource_conflict(const struct resource *res)
{
struct acpi_res_list *res_list_elem;
int ioport;
--- linux-2.6.32-rc6.orig/include/linux/acpi.h 2009-09-28 10:29:17.000000000 +0200
+++ linux-2.6.32-rc6/include/linux/acpi.h 2009-11-11 15:13:09.000000000 +0100
@@ -240,7 +240,7 @@ extern int pnpacpi_disabled;
#define PXM_INVAL (-1)
#define NID_INVAL (-1)
-int acpi_check_resource_conflict(struct resource *res);
+int acpi_check_resource_conflict(const struct resource *res);
int acpi_check_region(resource_size_t start, resource_size_t n,
const char *name);
--
Jean Delvare
next reply other threads:[~2009-11-11 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 14:22 Jean Delvare [this message]
2009-11-25 4:52 ` [PATCH] acpi_check_resource_conflict doesn't change the resource Len Brown
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=20091111152215.66617c8f@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.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