From: SF Markus Elfring <elfring@users.sourceforge.net>
To: kernel-janitors@vger.kernel.org,
"Gregory Clement" <gregory.clement@free-electrons.com>,
"Jan Lübbe" <jlu@pengutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>, trivial@kernel.org
Subject: [PATCH 2/2] mvebu-mbus: Fix a typo in five comment lines
Date: Fri, 12 Jan 2018 18:00:28 +0100 [thread overview]
Message-ID: <0d0d1f9a-55e8-3a40-9ea7-e7496b72fe7a@users.sourceforge.net> (raw)
In-Reply-To: <4796228f-fa7f-24db-0049-2d2b9041c5b0@users.sourceforge.net>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Fri, 12 Jan 2018 17:44:48 +0100
Adjust words in these descriptions.
Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
drivers/bus/mvebu-mbus.c | 19 +++++++++----------
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/drivers/bus/mvebu-mbus.c b/drivers/bus/mvebu-mbus.c
index 5844901aea0b..e0c1b07108a6 100644
--- a/drivers/bus/mvebu-mbus.c
+++ b/drivers/bus/mvebu-mbus.c
@@ -23,15 +23,14 @@
*
* This driver:
*
- * - Reads out the SDRAM address decoding windows at initialization
- * time, and fills the mvebu_mbus_dram_info structure with these
- * informations. The exported function mv_mbus_dram_info() allow
- * device drivers to get those informations related to the SDRAM
- * address decoding windows. This is because devices also have their
- * own windows (configured through registers that are part of each
- * device register space), and therefore the drivers for Marvell
- * devices have to configure those device -> SDRAM windows to ensure
- * that DMA works properly.
+ * - Reads out the SDRAM address decoding windows at initialization time,
+ * and fills the mvebu_mbus_dram_info structure with this information.
+ * The exported function mv_mbus_dram_info() allows device drivers to get
+ * this information related to the SDRAM address decoding windows.
+ * This is because devices also have their own windows (configured through
+ * registers that are part of each device register space), and therefore
+ * the drivers for Marvell devices have to configure those device
+ * -> SDRAM windows to ensure that DMA works properly.
*
* - Provides an API for platform code or device drivers to
* dynamically add or remove address decoding windows for the CPU ->
@@ -123,7 +122,7 @@ struct mvebu_mbus_soc_data {
};
/*
- * Used to store the state of one MBus window accross suspend/resume.
+ * Used to store the state of one MBus window across suspend/resume.
*/
struct mvebu_mbus_win_data {
u32 ctrl;
--
2.15.1
prev parent reply other threads:[~2018-01-12 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 16:57 [PATCH 0/2] mvebu-mbus: Adjustments for mvebu_devs_debug_show() SF Markus Elfring
2018-01-12 16:58 ` [PATCH 1/2] mvebu-mbus: Use seq_putc() in mvebu_devs_debug_show() SF Markus Elfring
2018-01-12 17:00 ` SF Markus Elfring [this message]
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=0d0d1f9a-55e8-3a40-9ea7-e7496b72fe7a@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=gregory.clement@free-electrons.com \
--cc=jlu@pengutronix.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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
Powered by JetHome