linux-kernel - Re: [PATCH] staging: vme_user: changed geoid data type from int to u32

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2024090325-amusing-sauna-1a74@gregkh>
Date: Tue, 3 Sep 2024 10:35:41 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Riyan Dhiman <riyandhiman14@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-staging@...ts.linux.dev
Subject: Re: [PATCH] staging: vme_user: changed geoid data type from int to
 u32

On Fri, Aug 30, 2024 at 10:48:07AM +0530, Riyan Dhiman wrote:
> Geoid is a module parameter which is set by root user.
> Its valid values are between 0 and VME_MAX_SLOTS. So, changing data type
> of geoid from int to u32 since it will always be positive.
> 
> Signed-off-by: Riyan Dhiman <riyandhiman14@...il.com>
> ---
>  drivers/staging/vme_user/vme_fake.c   | 6 +++---
>  drivers/staging/vme_user/vme_tsi148.c | 6 +++---
>  2 files changed, 6 insertions(+), 6 deletions(-)

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- This looks like a new version of a previously submitted patch, but you
  did not list below the --- line any changes from the previous version.
  Please read the section entitled "The canonical patch format" in the
  kernel file, Documentation/process/submitting-patches.rst for what
  needs to be done here to properly describe this.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot