public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Omer Faruk BULUT <m.omerfarukbulut@gmail.com>
Cc: dpenkler@gmail.com, arnd@arndb.de, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: gpib/common/gpib_os.c - Remove unnecessary OOM message
Date: Mon, 4 Nov 2024 00:45:15 +0100	[thread overview]
Message-ID: <2024110458-tank-very-49c4@gregkh> (raw)
In-Reply-To: <20241022180620.12429-1-m.omerfarukbulut@gmail.com>

On Tue, Oct 22, 2024 at 09:06:20PM +0300, Omer Faruk BULUT wrote:
> It duplicate the MM subsystem generic OOM message. This patch fixes the following checkpatch warning.

Please wrap your changelog text at 72 columns.

> 
>     WARNING: Possible unnecessary 'out of memory' message
> 
> Also, this patch itself might teach to module writers or readers that they have to give attention to MM subsystem
> even they interest another one.

I do not understand this comment at all, sorry, what does it have to do
with the change happening in this proposal?

> 
> Signed-off-by: Omer Faruk BULUT <m.omerfarukbulut@gmail.com>
> ---
>  drivers/staging/gpib/common/gpib_os.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/staging/gpib/common/gpib_os.c b/drivers/staging/gpib/common/gpib_os.c
> index 6b12404efe7d..27654b2180a5 100644
> --- a/drivers/staging/gpib/common/gpib_os.c
> +++ b/drivers/staging/gpib/common/gpib_os.c
> @@ -2093,10 +2093,9 @@ void gpib_register_driver(gpib_interface_t *interface, struct module *provider_m
>  	struct gpib_interface_list_struct *entry;
>  
>  	entry = kmalloc(sizeof(*entry), GFP_KERNEL);
> -	if (!entry) {
> -		pr_err("gpib: failed register %s interface, out of memory\n", interface->name);
> +	if (!entry) 
>  		return;
> -	}
> +	

You added trailing whitespace, ALWAYS run scripts/checkpatch.pl on
changes you are submitting to the kernel, you don't want to add a new
problem when trying to fix a different one :)

thanks,

greg k-h

      reply	other threads:[~2024-11-04  5:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 18:06 [PATCH] Staging: gpib/common/gpib_os.c - Remove unnecessary OOM message Omer Faruk BULUT
2024-11-03 23:45 ` Greg KH [this message]

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=2024110458-tank-very-49c4@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=dpenkler@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=m.omerfarukbulut@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox