All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: Sumitra Sharma <sumitraartsy@gmail.com>, <outreachy@lists.linux.dev>
Subject: Re: [PATCH] Staging: pi433: Change bit_rate type from u16 to u32
Date: Sun, 12 Mar 2023 18:34:55 -0700	[thread overview]
Message-ID: <640e7dbf181dc_229a8929410@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20230311114212.GA21407@ubuntu>

Sumitra Sharma wrote:
> Change bit_rate type from u16 to u32 inside struct pi433_tx_cfg to
> support bit rates up to 300kbps as per the spec.

From this commit log I'm still unclear by how this helps.

Where do the invalid values of bit_rate come from and how did the u16 value get
overflowed?

Ira

> 
> Signed-off-by: Sumitra Sharma <sumitraartsy@gmail.com>
> ---
>  drivers/staging/pi433/pi433_if.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/pi433/pi433_if.h b/drivers/staging/pi433/pi433_if.h
> index 25ee0b77a32c..1f8ffaf02d99 100644
> --- a/drivers/staging/pi433/pi433_if.h
> +++ b/drivers/staging/pi433/pi433_if.h
> @@ -51,7 +51,7 @@ enum option_on_off {
>  #define PI433_TX_CFG_IOCTL_NR	0
>  struct pi433_tx_cfg {
>  	__u32			frequency;
> -	__u16			bit_rate;
> +	__u32			bit_rate;
>  	__u32			dev_frequency;
>  	enum modulation		modulation;
>  	enum mod_shaping	mod_shaping;
> -- 
> 2.25.1
> 
> 



  parent reply	other threads:[~2023-03-13  1:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 11:42 [PATCH] Staging: pi433: Change bit_rate type from u16 to u32 Sumitra Sharma
2023-03-11 11:50 ` Julia Lawall
2023-03-11 11:59   ` Sumitra Sharma
2023-03-11 12:12     ` Julia Lawall
2023-03-13  1:34 ` Ira Weiny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-11 12:23 Sumitra Sharma
2023-03-11 12:31 ` Greg KH
2023-03-11 12:39 ` Dan Carpenter
2023-03-11 13:00   ` Sumitra Sharma
2023-03-11 13:17     ` Dan Carpenter

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=640e7dbf181dc_229a8929410@iweiny-mobl.notmuch \
    --to=ira.weiny@intel.com \
    --cc=outreachy@lists.linux.dev \
    --cc=sumitraartsy@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.