public inbox for kernelnewbies@kernelnewbies.org
 help / color / mirror / Atom feed
From: Marlon Rac Cambasis <marlonrc08@gmail.com>
To: kernelnewbies@kernelnewbies.org
Cc: marlonrc08@gmail.com
Subject: Please assess this patch: [PATCH] Docs: FIxed spelling errors in Documentation/devicetree/bindings/
Date: Fri, 4 Sep 2020 17:00:47 +1000	[thread overview]
Message-ID: <20200904070047.GA15414@slackware-L520.intranet> (raw)

Hello, I would like to make my first contribution to the Linux kernel in the
form of a (trivial) spelling fix. Does this patch (including the subject and the
way my mail is being displayed), meet the requirements? Furthermore, I think the
correct place to send it to would be devicetree@vger.kernel.org and also CCing 
it to trivial@kernel.org. Is this all okay? Should I send it to somewhere else,
do I need to make any changes? Also I don't need to add a body to the patch
when I send it do I?

Here is my patch:

Signed-off-by: Marlon Rac Cambasis <marlonrc08@gmail.com>
---
 Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt  | 2 +-
 Documentation/devicetree/bindings/reset/nuvoton,npcm-reset.txt | 2 +-
 Documentation/devicetree/bindings/watchdog/aspeed-wdt.txt      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt
index 70659c9..372f473 100644
--- a/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt
+++ b/Documentation/devicetree/bindings/pinctrl/samsung-pinctrl.txt
@@ -75,7 +75,7 @@ Required Properties:
   The child node should contain a list of pin(s) on which a particular pin
   function selection or pin configuration (or both) have to applied. This
   list of pins is specified using the property name "samsung,pins". There
-  should be atleast one pin specfied for this property and there is no upper
+  should be atleast one pin specified for this property and there is no upper
   limit on the count of pins that can be specified. The pins are specified
   using pin names which are derived from the hardware manual of the SoC. As
   an example, the pins in GPA0 bank of the pin controller can be represented
diff --git a/Documentation/devicetree/bindings/reset/nuvoton,npcm-reset.txt b/Documentation/devicetree/bindings/reset/nuvoton,npcm-reset.txt
index 6e80270..17b7a6a 100644
--- a/Documentation/devicetree/bindings/reset/nuvoton,npcm-reset.txt
+++ b/Documentation/devicetree/bindings/reset/nuvoton,npcm-reset.txt
@@ -9,7 +9,7 @@ Optional property:
 - nuvoton,sw-reset-number - Contains the software reset number to restart the SoC.
   NPCM7xx contain four software reset that represent numbers 1 to 4.
 
-  If 'nuvoton,sw-reset-number' is not specfied software reset is disabled.
+  If 'nuvoton,sw-reset-number' is not specified software reset is disabled.
 
 Example:
 	rstc: rstc@f0801000 {
diff --git a/Documentation/devicetree/bindings/watchdog/aspeed-wdt.txt b/Documentation/devicetree/bindings/watchdog/aspeed-wdt.txt
index d78d4a8f..a819763 100644
--- a/Documentation/devicetree/bindings/watchdog/aspeed-wdt.txt
+++ b/Documentation/devicetree/bindings/watchdog/aspeed-wdt.txt
@@ -20,7 +20,7 @@ Optional properties:
    This is useful in situations where another watchdog engine on chip is
    to perform the reset.
 
-   If 'aspeed,reset-type=' is not specfied the default is to enable system
+   If 'aspeed,reset-type=' is not specified the default is to enable system
    reset.
 
    Reset types:
-- 
2.9.0


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

             reply	other threads:[~2020-09-04  7:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04  7:00 Marlon Rac Cambasis [this message]
2020-09-04  9:54 ` Please assess this patch: [PATCH] Docs: FIxed spelling errors in Documentation/devicetree/bindings/ linux lover
2020-09-04 10:37 ` Greg KH
2020-09-04 13:29 ` Valdis Klētnieks

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=20200904070047.GA15414@slackware-L520.intranet \
    --to=marlonrc08@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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