All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aybuke Ozdemir <aybuke.147@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: Aybuke Ozdemir <aybuke.147@gmail.com>
Subject: [PATCH 2/2] Staging: wilc1000: Added 'function' word.
Date: Sun,  4 Oct 2015 17:04:20 +0300	[thread overview]
Message-ID: <1443967460-14302-2-git-send-email-aybuke.147@gmail.com> (raw)
In-Reply-To: <1443967460-14302-1-git-send-email-aybuke.147@gmail.com>

This patch organizing missing written word missing.
Found by checkpatch.pl:
CHECK: 'funcion' may be misspelled - perhaps 'function'?

Signed-off-by: Aybuke Ozdemir <aybuke.147@gmail.com>
---
 drivers/staging/wilc1000/coreconfigurator.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/wilc1000/coreconfigurator.c b/drivers/staging/wilc1000/coreconfigurator.c
index 439c828..08f5675 100644
--- a/drivers/staging/wilc1000/coreconfigurator.c
+++ b/drivers/staging/wilc1000/coreconfigurator.c
@@ -296,7 +296,7 @@ static inline u16 get_assoc_resp_cap_info(u8 *data)
 	return cap_info;
 }
 
-/* This funcion extracts the association status code from the incoming       */
+/* This function extracts the association status code from the incoming       */
 /* association response frame and returns association status code            */
 static inline u16 get_asoc_status(u8 *data)
 {
-- 
2.1.4



  reply	other threads:[~2015-10-04 14:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04 14:04 [PATCH 1/2] Staging: wilc1000: Do not use multiple blank lines Aybuke Ozdemir
2015-10-04 14:04 ` Aybuke Ozdemir [this message]
2015-10-04 18:46   ` [Outreachy kernel] [PATCH 2/2] Staging: wilc1000: Added 'function' word Julia Lawall
2015-10-04 23:59     ` Aybuke Ozdemir
2015-10-05 10:55       ` Greg KH
2015-10-05 12:45       ` Julia Lawall

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=1443967460-14302-2-git-send-email-aybuke.147@gmail.com \
    --to=aybuke.147@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.