Re: [PATCH] staging: vme_user: fix lines exceeding 80 characters in vme_tsi148.c

[Greg KH <gregkh@linuxfoundation.org>]

On Sun, May 10, 2026 at 05:42:15PM +0000, Hanu-man12shaw wrote:
> Signed-off-by: Hanu-man12shaw <harshit116@gmail.com>
> ---
>  drivers/staging/vme_user/vme_tsi148.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/vme_user/vme_tsi148.c b/drivers/staging/vme_user/vme_tsi148.c
> index 4cf3486646ce..0e8a67fbf562 100644
> --- a/drivers/staging/vme_user/vme_tsi148.c
> +++ b/drivers/staging/vme_user/vme_tsi148.c
> @@ -755,7 +755,8 @@ static int tsi148_alloc_resource(struct vme_master_resource *image,
>  					size, 0x10000, PCIBIOS_MIN_MEM,
>  					0, NULL, NULL);
>  	if (retval) {
> -		dev_err(tsi148_bridge->parent, "Failed to allocate mem resource for window %d size 0x%lx start 0x%lx\n",
> +		dev_err(tsi148_bridge->parent,
> +			"Failed to allocate mem resource for window %d size 0x%lx start 0x%lx\n",
>  			image->number, (unsigned long)size,
>  			(unsigned long)image->bus_resource.start);
>  		goto err_resource;
> @@ -2252,7 +2253,8 @@ static int tsi148_probe(struct pci_dev *pdev, const struct pci_device_id *id)
>  	struct vme_lm_resource *lm;
>  
>  	if (geoid >= VME_MAX_SLOTS) {
> -		dev_err(&pdev->dev, "VME geographical address must be between 0 and %d (exclusive), but got %d\n",
> +		dev_err(&pdev->dev,
> +			"VME geographical address must be between 0 and %d (exclusive), but got %d\n",
>  			VME_MAX_SLOTS, geoid);
>  		return -EINVAL;
>  	}
> -- 
> 2.53.0
> 
> 

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:

- You sent multiple patches, yet no indication of which ones should be
  applied in which order.  Greg could just guess, but if you are
  receiving this email, he guessed wrong and the patches didn't apply.
  Please read the section entitled "The canonical patch format" in the
  kernel file, Documentation/process/submitting-patches.rst for a
  description of how to do this so that Greg has a chance to apply these
  correctly.

- You did not specify a description of why the patch is needed, or
  possibly, any description at all, in the email body.  Please read the
  section entitled "The canonical patch format" in the kernel file,
  Documentation/process/submitting-patches.rst for what is needed in
  order to properly describe the change.

- It looks like you did not use your "real" name for the patch on either
  the Signed-off-by: line, or the From: line (both of which have to
  match).  Please read the kernel file,
  Documentation/process/submitting-patches.rst for how to do this
  correctly.

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