From: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
To: broonie@kernel.org
Cc: gregkh@linuxfoundation.org, rafael@kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 1/6] regmap-irq: Fix typo in documentation for .get_irq_reg()
Date: Tue, 9 May 2023 12:00:55 +0100 [thread overview]
Message-ID: <20230509110100.3980123-2-aidanmacdonald.0x0@gmail.com> (raw)
In-Reply-To: <20230509110100.3980123-1-aidanmacdonald.0x0@gmail.com>
It refers to a non-existent "num_type_settings" value, which is
an old name I'd used during development of config registers and
later dropped because it wasn't very clear.
The correct bound for the range is num_config_regs, which can
be verified by checking the implementation.
Signed-off-by: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
---
include/linux/regmap.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/regmap.h b/include/linux/regmap.h
index c2b9cc5db824..45fdb6e93617 100644
--- a/include/linux/regmap.h
+++ b/include/linux/regmap.h
@@ -1606,7 +1606,7 @@ struct regmap_irq_chip_data;
* addresses. The base register will be one of @status_base,
* @mask_base, etc., @main_status, or any of @config_base.
* The index will be in the range [0, num_main_regs[ for the
- * main status base, [0, num_type_settings[ for any config
+ * main status base, [0, num_config_regs[ for any config
* register base, and [0, num_regs[ for any other base.
* If unspecified then regmap_irq_get_irq_reg_linear() is used.
* @irq_drv_data: Driver specific IRQ data which is passed as parameter when
--
2.39.2
next prev parent reply other threads:[~2023-05-09 11:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 11:00 [PATCH v1 0/6] regmap-irq: Cleanups and remove unused functionality Aidan MacDonald
2023-05-09 11:00 ` Aidan MacDonald [this message]
2023-05-09 11:00 ` [PATCH v1 2/6] regmap-irq: Remove virtual registers Aidan MacDonald
2023-05-09 11:00 ` [PATCH v1 3/6] regmap-irq: Remove type registers Aidan MacDonald
2023-05-11 1:24 ` Mark Brown
2023-05-11 9:09 ` Aidan MacDonald
2023-05-09 11:00 ` [PATCH v1 4/6] regmap-irq: Remove support for not_fixed_stride Aidan MacDonald
2023-05-09 11:00 ` [PATCH v1 5/6] regmap-irq: Minor adjustments to .handle_mask_sync() Aidan MacDonald
2023-05-09 11:01 ` [PATCH v1 6/6] regmap-irq: Drop backward compatibility for inverted mask/unmask Aidan MacDonald
2023-05-11 5:43 ` [PATCH v1 0/6] regmap-irq: Cleanups and remove unused functionality Mark 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=20230509110100.3980123-2-aidanmacdonald.0x0@gmail.com \
--to=aidanmacdonald.0x0@gmail.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.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
all inboxes | Powered by JetHome®