mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: Darshan Rathod <darshanrathod475@gmail.com>
Cc: hsweeten@visionengravers.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: comedi: das16 : fixed a struct warning in code
Date: Mon, 28 Apr 2025 11:44:16 +0100	[thread overview]
Message-ID: <d0feff64-af96-41f8-9c52-3dafeafd7871@mev.co.uk> (raw)
In-Reply-To: <20250426094145.13564-1-darshanrathod475@gmail.com>

On 26/04/2025 10:41, Darshan Rathod wrote:
> fixed a warning messages for a struct
> Signed-off-by: Darshan Rathod <darshanrathod475@gmail.com>

There should be a blank line before that "Signed-off-by" line.

The patch subject should not have the "staging:" tag since the code has 
been moved out of the "drivers/staging" directory.

> ---
>   drivers/comedi/drivers/das16.c | 8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/comedi/drivers/das16.c b/drivers/comedi/drivers/das16.c
> index f5ca6c0d4d0c..73717f75d60f 100644
> --- a/drivers/comedi/drivers/das16.c
> +++ b/drivers/comedi/drivers/das16.c
> @@ -956,8 +956,8 @@ static const struct comedi_lrange *das16_ai_range(struct comedi_device *dev,
>   
>   	/* get any user-defined input range */
>   	if (pg_type == das16_pg_none && (min || max)) {
> -		struct comedi_lrange *lrange;
> -		struct comedi_krange *krange;
> +		const struct comedi_lrange *lrange;
> +		const struct comedi_krange *krange;
>   
>   		/* allocate single-range range table */
>   		lrange = comedi_alloc_spriv(s,
> @@ -990,8 +990,8 @@ static const struct comedi_lrange *das16_ao_range(struct comedi_device *dev,
>   
>   	/* get any user-defined output range */
>   	if (min || max) {
> -		struct comedi_lrange *lrange;
> -		struct comedi_krange *krange;
> +		const struct comedi_lrange *lrange;
> +		const struct comedi_krange *krange;
>   
>   		/* allocate single-range range table */
>   		lrange = comedi_alloc_spriv(s,

I do not see how these changes will fix any warning messages.  In fact, 
they will produce compiler errors from the code further down the functions.

-- 
-=( Ian Abbott <abbotti@mev.co.uk> || MEV Ltd. is a company  )=-
-=( registered in England & Wales.  Regd. number: 02862268.  )=-
-=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=-
-=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=-

  reply	other threads:[~2025-04-28 12:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-26  9:41 Darshan Rathod
2025-04-28 10:44 ` Ian Abbott [this message]
2025-05-07  5:49 ` 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=d0feff64-af96-41f8-9c52-3dafeafd7871@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=darshanrathod475@gmail.com \
    --cc=hsweeten@visionengravers.com \
    --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

all inboxes | Powered by JetHome®