mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: sayli karnik <karniksayli1995@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] Documentation: phy: Fix repetition of word 'the'
Date: Thu, 9 Mar 2017 12:23:16 +0530	[thread overview]
Message-ID: <3559f33444fbae6fda8e11ea00c0dfe3b7dc46b2.1489039271.git.karniksayli1995@gmail.com> (raw)
In-Reply-To: <cover.1489039271.git.karniksayli1995@gmail.com>

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

  reply	other threads:[~2017-03-09  6:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09  6:52 [PATCH 0/3] Fix unintentional repetition of words sayli karnik
2017-03-09  6:53 ` sayli karnik [this message]
2017-03-09  6:53 ` [PATCH 2/3] Documentation: ABI: testing: sysfs-bus-pci: Fix repetition of word 'the' sayli karnik
2017-03-09  6:54 ` [PATCH 3/3] Documentation: cpu-freq: cpu-drivers: Fix repetition of word 'to' sayli karnik
2017-03-09  9:15   ` Viresh Kumar

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=3559f33444fbae6fda8e11ea00c0dfe3b7dc46b2.1489039271.git.karniksayli1995@gmail.com \
    --to=karniksayli1995@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.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®