From: Greg KH <gregkh@linuxfoundation.org>
To: Luke Koch <lu.ale.koch@gmail.com>
Cc: error27@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: wlan-ng: replace rate macros
Date: Thu, 20 Apr 2023 13:55:03 +0200 [thread overview]
Message-ID: <ZEEoFxsTuAxAS7Ep@kroah.com> (raw)
In-Reply-To: <ZD6OqBOp1ezQDgMu@kernelhacking.kernelhacking.example.com>
On Tue, Apr 18, 2023 at 02:35:52PM +0200, Luke Koch wrote:
> Change p80211msg_dot11req_scan_results rate members to struct arrays
> instead of individually numbered member structs.
> Replace macros to set rates with loops to avoid checkpatch warning
> and adhere to linux coding style.
>
> Reported by checkpatch:
>
> CHECK: Macro argument reuse 'N' - possible side-effects?
>
> Signed off by: Luke Koch <lu.ale.koch@gmail.com>
Resend without the odd reply-to...
This has to be "Signed-off-by:"
prev parent reply other threads:[~2023-04-20 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 12:35 [PATCH v3] staging: wlan-ng: replace rate macros Luke Koch
2023-04-18 13:04 ` Greg KH
2023-04-18 19:38 ` Luke Koch
2023-04-20 11:54 ` Greg KH
2023-04-20 11:55 ` Greg KH [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=ZEEoFxsTuAxAS7Ep@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lu.ale.koch@gmail.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.