linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Leonardo Araujo <leonardo.aa88@gmail.com>
Cc: Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
	linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] Staging: r8188eu: core: alignment should match open parenthesis
Date: Tue, 8 Feb 2022 10:43:50 +0100	[thread overview]
Message-ID: <YgI7VtmUtD0nJ2O0@kroah.com> (raw)
In-Reply-To: <20220207234824.27893-1-leonardo.aa88@gmail.com>

On Mon, Feb 07, 2022 at 08:48:24PM -0300, Leonardo Araujo wrote:
> Fixed a coding style issue.
> 
> Signed-off-by: Leonardo Araujo <leonardo.aa88@gmail.com>
> ---
>  drivers/staging/r8188eu/core/rtw_ap.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/staging/r8188eu/core/rtw_ap.c b/drivers/staging/r8188eu/core/rtw_ap.c
> index e02dd8e11c95..c7803144355a 100644
> --- a/drivers/staging/r8188eu/core/rtw_ap.c
> +++ b/drivers/staging/r8188eu/core/rtw_ap.c
> @@ -942,8 +942,8 @@ void bss_cap_update_on_sta_join(struct adapter *padapter, struct sta_info *psta)
>  				pmlmepriv->num_sta_ht_no_gf++;
>  			}
>  			DBG_88E("%s STA %pM - no greenfield, num of non-gf stations %d\n",
> -				   __func__, (psta->hwaddr),
> -				   pmlmepriv->num_sta_ht_no_gf);
> +				__func__, (psta->hwaddr),
> +				pmlmepriv->num_sta_ht_no_gf);
>  		}
>  
>  		if ((ht_capab & IEEE80211_HT_CAP_SUP_WIDTH_20_40) == 0) {
> @@ -952,8 +952,8 @@ void bss_cap_update_on_sta_join(struct adapter *padapter, struct sta_info *psta)
>  				pmlmepriv->num_sta_ht_20mhz++;
>  			}
>  			DBG_88E("%s STA %pM - 20 MHz HT, num of 20MHz HT STAs %d\n",
> -				   __func__, (psta->hwaddr),
> -				   pmlmepriv->num_sta_ht_20mhz);
> +				__func__, (psta->hwaddr),
> +				pmlmepriv->num_sta_ht_20mhz);
>  		}
>  	} else {
>  		if (!psta->no_ht_set) {
> -- 
> 2.29.0
> 
> 

This patch does not apply to my tree at all.  What tree/branch did you
make it against?

Always work against linux-next at the very least, and the subsystem
development branch usually, so that you do not duplicate work that
others have already done.

thanks,

greg k-h

  reply	other threads:[~2022-02-08  9:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 23:48 [PATCH] Staging: r8188eu: core: alignment should match open parenthesis Leonardo Araujo
2022-02-08  9:43 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-09 20:45 [PATCH] Staging: r8188eu: core: Alignment " Leonardo Araujo

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=YgI7VtmUtD0nJ2O0@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=leonardo.aa88@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=phil@philpotter.co.uk \
    /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).