linux-kernel - [PATCH 2/2] mvebu-mbus: Fix a typo in five comment lines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 12 Jan 2018 18:00:28 +0100
From:   SF Markus Elfring <elfring@...rs.sourceforge.net>
To:     kernel-janitors@...r.kernel.org,
        Gregory Clement <gregory.clement@...e-electrons.com>,
        Jan Lübbe <jlu@...gutronix.de>
Cc:     LKML <linux-kernel@...r.kernel.org>, trivial@...nel.org
Subject: [PATCH 2/2] mvebu-mbus: Fix a typo in five comment lines

From: Markus Elfring <elfring@...rs.sourceforge.net>
Date: Fri, 12 Jan 2018 17:44:48 +0100

Adjust words in these descriptions.

Signed-off-by: Markus Elfring <elfring@...rs.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