[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180506112404.24872-1-wsa+renesas@sang-engineering.com>
Date: Sun, 6 May 2018 13:23:44 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: trivial@...nel.org
Cc: linux-renesas-soc@...r.kernel.org,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
devicetree@...r.kernel.org, linux-hwmon@...r.kernel.org,
linux-i2c@...r.kernel.org, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-ntb@...glegroups.com,
linuxppc-dev@...ts.ozlabs.org, netdev@...r.kernel.org,
reiserfs-devel@...r.kernel.org
Subject: [PATCH 0/9] tree-wide: fix typo 'can by' to 'can be'
I found this kind of typo when reading the documentation for device_remove().
So, I checked the tree for it.
CCing all the subsystems directly, and I'd think the leftover ones could be
picked up by the trivial tree. Or would it be more convenient if trivial would
pick up all? I don't mind.
Based on v4.17-rc3.
Wolfram Sang (9):
dt-bindings: i2c: fix typo 'can by' to 'can be'
powerpc/watchdog: fix typo 'can by' to 'can be'
base: core: fix typo 'can by' to 'can be'
hwmon: fschmd: fix typo 'can by' to 'can be'
input: ati_remote2: fix typo 'can by' to 'can be'
NTB: ntb_hw_idt: fix typo 'can by' to 'can be'
reiserfs: journal: fix typo 'can by' to 'can be'
net: flow_dissector: fix typo 'can by' to 'can be'
objtool: fix typo 'can by' to 'can be'
Documentation/devicetree/bindings/i2c/i2c-davinci.txt | 2 +-
arch/powerpc/kernel/watchdog.c | 2 +-
drivers/base/core.c | 2 +-
drivers/hwmon/fschmd.c | 2 +-
drivers/input/misc/ati_remote2.c | 2 +-
drivers/ntb/hw/idt/ntb_hw_idt.c | 2 +-
fs/reiserfs/journal.c | 2 +-
include/net/flow_dissector.h | 2 +-
tools/objtool/Documentation/stack-validation.txt | 2 +-
9 files changed, 9 insertions(+), 9 deletions(-)
--
2.11.0
Powered by blists - more mailing lists