linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Mairo Paul Rufus <akoudanilo@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	trivial@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: wlan-ng: Fix comments typos
Date: Thu, 18 Feb 2021 19:15:39 +0300	[thread overview]
Message-ID: <20210218161538.GO2087@kadam> (raw)
In-Reply-To: <20210210145952.722586-1-akoudanilo@gmail.com>

On Wed, Feb 10, 2021 at 03:59:52PM +0100, Mairo Paul Rufus wrote:
> Signed-off-by: Mairo Paul Rufus <akoudanilo@gmail.com>

No commit message.  It should say something like:

Checkpatch complained about the accidental repeated words like
"our our" so I fixed it.

> diff --git a/drivers/staging/wlan-ng/prism2sta.c b/drivers/staging/wlan-ng/prism2sta.c
> index 8f25496188aa..e6dcb687e7a1 100644
> --- a/drivers/staging/wlan-ng/prism2sta.c
> +++ b/drivers/staging/wlan-ng/prism2sta.c
> @@ -461,7 +461,7 @@ u32 prism2sta_ifstate(struct wlandevice *wlandev, u32 ifstate)
>  		case WLAN_MSD_FWLOAD:
>  			wlandev->msdstate = WLAN_MSD_RUNNING_PENDING;
>  			/* Initialize the device+driver for full
> -			 * operation. Note that this might me an FWLOAD to
> +			 * operation. Note that this might me an FWLOAD
                                                     ^^^^^^^^
This probably should be "might be".


>  			 * to RUNNING transition so we must not do a chip
>  			 * or board level reset.  Note that on failure,
>  			 * the MSD state is set to HWPRESENT because we

regards,
dan carpenter

      parent reply	other threads:[~2021-02-18 18:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 14:59 [PATCH] staging: wlan-ng: Fix comments typos Mairo Paul Rufus
2021-02-10 17:04 ` Greg KH
2021-02-11 16:55   ` Mairo P. Rufus
2021-02-11 17:28     ` Greg KH
2021-02-18 16:15 ` Dan Carpenter [this message]

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=20210218161538.GO2087@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=akoudanilo@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@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;
as well as URLs for NNTP newsgroup(s).