linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tawah Peggy <tawahpeggy98@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Kroah-Hartman <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH v2] Staging:wlan-ng:cfg80211: A better fix for: Lines should end with a '('
Date: Mon, 13 Sep 2021 19:04:04 +0100	[thread overview]
Message-ID: <20210913180404.GA325222@peggy-InsydeH2O-EFI-BIOS> (raw)

<greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Bcc: 
Subject: [PATCH v2] Staging: wlan-ng: cfg80211: A better fix for: Lines should
 not end with a '('.
Reply-To: 

This patch fixes the checkpatch error : lines should not end with a '('
by reducing length of function name to enable the arguments be passed on a single line.

Signed-off-by: Tawah Peggy <tawahpeggy98@gmail.com>
---
 drivers/staging/wlan-ng/cfg80211.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/staging/wlan-ng/cfg80211.c b/drivers/staging/wlan-ng/cfg80211.c
index 7951bd63816f..711c88c59e78 100644
--- a/drivers/staging/wlan-ng/cfg80211.c
+++ b/drivers/staging/wlan-ng/cfg80211.c
@@ -328,8 +328,7 @@ static int prism2_scan(struct wiphy *wiphy,
 		(i < request->n_channels) && i < ARRAY_SIZE(prism2_channels);
 		i++)
 		msg1.channellist.data.data[i] =
-			ieee80211_frequency_to_channel(
-				request->channels[i]->center_freq);
+			ieee80211_freq_to_channel(request->channels[i]->center_freq);
 	msg1.channellist.data.len = request->n_channels;
 
 	msg1.maxchanneltime.data = 250;
-- 
2.25.1


             reply	other threads:[~2021-09-13 18:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 18:04 Tawah Peggy [this message]
2021-09-14  2:04 ` [PATCH v2] Staging:wlan-ng:cfg80211: A better fix for: Lines should end with a '(' kernel test robot

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=20210913180404.GA325222@peggy-InsydeH2O-EFI-BIOS \
    --to=tawahpeggy98@gmail.com \
    --cc=greg@kroah.com \
    --cc=gregkh@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).