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 v2] Staging: gpib: gpib_os.c - Remove unnecessary OOM message
Date: Fri, 8 Nov 2024 04:50:16 +0100 [thread overview]
Message-ID: <2024110805-lived-grit-433c@gregkh> (raw)
In-Reply-To: <20241107213813.19185-1-m.omerfarukbulut@gmail.com>
On Fri, Nov 08, 2024 at 12:38:12AM +0300, Omer Faruk BULUT wrote:
> It duplicate the MM subsystem generic OOM message. This patch fixes
> the following checkpatch warning.
>
> WARNING: Possible unnecessary 'out of memory' message
>
> Signed-off-by: Omer Faruk BULUT <m.omerfarukbulut@gmail.com>
That is not what this patch does at all :(
prev parent reply other threads:[~2024-11-08 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 21:38 [PATCH v2] Staging: gpib: gpib_os.c - Remove unnecessary OOM message Omer Faruk BULUT
2024-11-08 3:50 ` 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=2024110805-lived-grit-433c@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