[PATCH 0/3] Fix unintentional repetition of words

[PATCH 0/3] Fix unintentional repetition of words

[sayli karnik]

Fix typos in the form of consecutive repetition of words.

sayli karnik (3):
  Documentation: phy: Fix repetition of word 'the'
  Documentation: ABI: testing: sysfs-bus-pci: Fix repetition of word
    'the'
  Documentation: cpu-freq: cpu-drivers: Fix repetition of word 'to'

 Documentation/ABI/testing/sysfs-bus-pci | 2 +-
 Documentation/cpu-freq/cpu-drivers.txt  | 2 +-
 Documentation/phy.txt                   | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

-- 
2.7.4

[PATCH 1/3] Documentation: phy: Fix repetition of word 'the'

[sayli karnik]

The patch replaces 'the the' with 'the' in the documantation.

Signed-off-by: sayli karnik <karniksayli1995@gmail.com>
---
 Documentation/phy.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/phy.txt b/Documentation/phy.txt
index 0aa994b..383cdd8 100644
--- a/Documentation/phy.txt
+++ b/Documentation/phy.txt
@@ -97,7 +97,7 @@ should contain the phy name as given in the dt data and in the case of
 non-dt boot, it should contain the label of the PHY.  The two
 devm_phy_get associates the device with the PHY using devres on
 successful PHY get. On driver detach, release function is invoked on
-the the devres data and devres data is freed. phy_optional_get and
+the devres data and devres data is freed. phy_optional_get and
 devm_phy_optional_get should be used when the phy is optional. These
 two functions will never return -ENODEV, but instead returns NULL when
 the phy cannot be found.Some generic drivers, such as ehci, may use multiple
-- 
2.7.4

[PATCH 2/3] Documentation: ABI: testing: sysfs-bus-pci: Fix repetition of word 'the'

[sayli karnik]

The patch replaces 'the the' with 'the' in the documentation.

Signed-off-by: sayli karnik <karniksayli1995@gmail.com>
---
 Documentation/ABI/testing/sysfs-bus-pci | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/ABI/testing/sysfs-bus-pci b/Documentation/ABI/testing/sysfs-bus-pci
index 5a1732b..e4e9010 100644
--- a/Documentation/ABI/testing/sysfs-bus-pci
+++ b/Documentation/ABI/testing/sysfs-bus-pci
@@ -299,5 +299,5 @@ What:		/sys/bus/pci/devices/.../revision
 Date:		November 2016
 Contact:	Emil Velikov <emil.l.velikov@gmail.com>
 Description:
-		This file contains the revision field of the the PCI device.
+		This file contains the revision field of the PCI device.
 		The value comes from device config space. The file is read only.
-- 
2.7.4

[PATCH 3/3] Documentation: cpu-freq: cpu-drivers: Fix repetition of word 'to'

[sayli karnik]

The patch replaces 'to to' with 'to' in the documentation.

Signed-off-by: sayli karnik <karniksayli1995@gmail.com>
---
 Documentation/cpu-freq/cpu-drivers.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/cpu-freq/cpu-drivers.txt b/Documentation/cpu-freq/cpu-drivers.txt
index f71e6be..434c49c 100644
--- a/Documentation/cpu-freq/cpu-drivers.txt
+++ b/Documentation/cpu-freq/cpu-drivers.txt
@@ -231,7 +231,7 @@ the reference implementation in drivers/cpufreq/longrun.c
 Only for drivers with target_index() and CPUFREQ_ASYNC_NOTIFICATION unset.
 
 get_intermediate should return a stable intermediate frequency platform wants to
-switch to, and target_intermediate() should set CPU to to that frequency, before
+switch to, and target_intermediate() should set CPU to that frequency, before
 jumping to the frequency corresponding to 'index'. Core will take care of
 sending notifications and driver doesn't have to handle them in
 target_intermediate() or target_index().
-- 
2.7.4

Re: [PATCH 3/3] Documentation: cpu-freq: cpu-drivers: Fix repetition of word 'to'

[Viresh Kumar]

On Thu, Mar 9, 2017 at 12:24 PM, sayli karnik <karniksayli1995@gmail.com> wrote:
> The patch replaces 'to to' with 'to' in the documentation.
>
> Signed-off-by: sayli karnik <karniksayli1995@gmail.com>
> ---
>  Documentation/cpu-freq/cpu-drivers.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>