mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Raymond L. Rivera" <ray.l.rivera@gmail.com>
To: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Raymond L. Rivera" <ray.l.rivera@gmail.com>
Subject: [PATCH 1/2] CodingStyle: Fixed a minor typo.
Date: Thu, 24 Jul 2014 02:39:44 -0700	[thread overview]
Message-ID: <1406194785-19596-2-git-send-email-ray.l.rivera@gmail.com> (raw)
In-Reply-To: <1406194785-19596-1-git-send-email-ray.l.rivera@gmail.com>

There was a minor typo in the CodingStyle document where the word 'section'
had been spelled as 'secton'.

Signed-off-by: Raymond L. Rivera <ray.l.rivera@gmail.com>
---
 Documentation/CodingStyle | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
index 6b6bef3..3171822 100644
--- a/Documentation/CodingStyle
+++ b/Documentation/CodingStyle
@@ -675,7 +675,7 @@ the ones already enabled by DEBUG.
 Many subsystems have Kconfig debug options to turn on -DDEBUG in the
 corresponding Makefile; in other cases specific files #define DEBUG.  And
 when a debug message should be unconditionally printed, such as if it is
-already inside a debug-related #ifdef secton, printk(KERN_DEBUG ...) can be
+already inside a debug-related #ifdef section, printk(KERN_DEBUG ...) can be
 used.
 
 
-- 
1.9.1


  reply	other threads:[~2014-07-24  9:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24  9:39 [PATCH 0/2] Minor documentation typo fixes Raymond L. Rivera
2014-07-24  9:39 ` Raymond L. Rivera [this message]
2014-07-25 19:51   ` [PATCH 1/2] CodingStyle: Fixed a minor typo Randy Dunlap
2014-07-24  9:39 ` [PATCH 2/2] linux/pagemap.h: Fixed a typo in a code comment Raymond L. Rivera
2014-07-25 19:51   ` Randy Dunlap
2014-07-25 19:50 ` [PATCH 0/2] Minor documentation typo fixes Randy Dunlap

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=1406194785-19596-2-git-send-email-ray.l.rivera@gmail.com \
    --to=ray.l.rivera@gmail.com \
    --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®