public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guru Mehar Rachaputi <gurumeharrachaputi@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: pi433: modify bit_rate from u16 to u32
Date: Tue, 31 Jan 2023 06:22:23 +0100	[thread overview]
Message-ID: <Y9ilj812USHrSXe+@kroah.com> (raw)
In-Reply-To: <Y9h42l/8EcPqn63x@combine-ThinkPad-S1-Yoga>

On Tue, Jan 31, 2023 at 03:11:38AM +0100, Guru Mehar Rachaputi wrote:
> (struct pi433_tx_cfg)->bit_rate is modified from u16 to u32 to
> support bit rates up to 300kbps per the spec

What spec?

And how can changing the size of a variable that crosses the user/kernel
boundry like this change the bit rate max?

> 
> Signed-off-by: Guru Mehar Rachaputi <gurumeharrachaputi@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;

And didn't you just break existing userspace code?  If not, how?  If so,
how did you test this?

thanks,

greg k-h

  reply	other threads:[~2023-01-31  5:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31  2:11 [PATCH] staging: pi433: modify bit_rate from u16 to u32 Guru Mehar Rachaputi
2023-01-31  5:22 ` Greg Kroah-Hartman [this message]
2023-01-31 10:19   ` Guru Mehar Rachaputi
2023-01-31 10:41     ` Greg Kroah-Hartman
2023-01-31 10:52       ` Guru Mehar Rachaputi
2023-01-31 11:14         ` Dan Carpenter
2023-01-31 18:18           ` Guru Mehar Rachaputi
2023-02-01 12:34     ` David Laight
2023-02-01 13:22       ` Dan Carpenter
2023-02-02 22:02         ` David Laight
2023-02-02 22:13           ` 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=Y9ilj812USHrSXe+@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=gurumeharrachaputi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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