All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v2 06/13] wiphy: add two regulatory domain state events
Date: Thu, 4 Aug 2022 10:31:08 -0500	[thread overview]
Message-ID: <dac673fe-cebb-31cf-4885-426fec523e35@gmail.com> (raw)
In-Reply-To: <20220803213644.277534-6-prestwoj@gmail.com>

Hi James,

On 8/3/22 16:36, James Prestwood wrote:
> Events to indicate when a regulatory domain wiphy dump has
> started and ended. This is important because certain actions
> such as scanning need to be delayed until the dump has finished.
> ---
>   src/device.c | 2 ++
>   src/wiphy.h  | 2 ++
>   2 files changed, 4 insertions(+)
> 
> diff --git a/src/device.c b/src/device.c
> index 02da2cdc..d7eb6adb 100644
> --- a/src/device.c
> +++ b/src/device.c
> @@ -282,6 +282,8 @@ static void device_wiphy_state_changed_event(struct wiphy *wiphy,
>   			netdev_set_powered(device->netdev, true,
>   							NULL, NULL, NULL);
>   		break;
> +	default:
> +		break;

nit: Prefer to not use default: when possible.  The reason is that if a new 
enumeration is added (like you do here), the compiler will warn when it isn't 
handled.  Prefer to be paranoid and explicitly add all the enumerations instead, 
so that any new enumerations are not left mistakenly unhandled.

>   	}
>   }
>   

I amended this patch to do the above and applied, thanks!

Regards,
-Denis

  reply	other threads:[~2022-08-04 15:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 21:36 [PATCH v2 01/13] wiphy: fix runtime error from bit shift James Prestwood
2022-08-03 21:36 ` [PATCH v2 02/13] scan: track scanned frequencies for entire request James Prestwood
2022-08-03 21:36 ` [PATCH v2 03/13] nl80211util: add nl80211_parse_supported_frequencies James Prestwood
2022-08-04 15:27   ` Denis Kenzior
2022-08-03 21:36 ` [PATCH v2 04/13] wiphy: track self-managed flag James Prestwood
2022-08-03 21:36 ` [PATCH v2 05/13] wiphy: use nl80211_parse_supported_frequencies James Prestwood
2022-08-03 21:36 ` [PATCH v2 06/13] wiphy: add two regulatory domain state events James Prestwood
2022-08-04 15:31   ` Denis Kenzior [this message]
2022-08-03 21:36 ` [PATCH v2 07/13] wiphy: dump wiphy's on regulatory domain change James Prestwood
2022-08-03 21:36 ` [PATCH v2 08/13] wiphy: add wiphy_regdom_is_updating James Prestwood
2022-08-03 21:36 ` [PATCH v2 09/13] wiphy: add wiphy_country_is_unknown James Prestwood
2022-08-04 16:48   ` Denis Kenzior
2022-08-03 21:36 ` [PATCH v2 10/13] station: do full passive scan if 6GHz is supported but disabled James Prestwood
2022-08-03 21:36 ` [PATCH v2 11/13] scan: split full scans by band to enable 6GHz James Prestwood
2022-08-03 21:36 ` [PATCH v2 12/13] scan: watch for regdom updates " James Prestwood
2022-08-03 21:36 ` [PATCH v2 13/13] wiphy: don't re-dump wiphy if the regdom didn't change James Prestwood

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=dac673fe-cebb-31cf-4885-426fec523e35@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=prestwoj@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.