From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Kushagra Verma <kushagra765@outlook.com>
Cc: balbi@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB / dwc3: remove a possible unnecessary 'out of memory' message
Date: Sun, 01 May 2022 09:50:45 -0700 [thread overview]
Message-ID: <8cf3b100a4dc0eaac9214e1a9ea2b6dace7c85bb.camel@perches.com> (raw)
In-Reply-To: <Ym6pp/O1fpneA5ZW@kroah.com>
On Sun, 2022-05-01 at 17:39 +0200, Greg KH wrote:
> On Sun, May 01, 2022 at 09:01:36PM +0530, Kushagra Verma wrote:
> > This patch removes a possible unnecessary out of memory message from
> > core.c
> > as reported by checkpatch.pl:
> > WARNING: Possible unnecessary 'out of memory' message
> 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:
>
> - Your patch is malformed (tabs converted to spaces, linewrapped, etc.)
> and can not be applied. Please read the file,
> Documentation/email-clients.txt in order to fix this.
Seems like a patch-bot false positive patch-bot to me.
next prev parent reply other threads:[~2022-05-01 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-01 15:31 [PATCH] USB / dwc3: remove a possible unnecessary 'out of memory' message Kushagra Verma
2022-05-01 15:39 ` Greg KH
2022-05-01 16:50 ` Joe Perches [this message]
2022-05-01 17:09 ` Greg KH
2022-05-01 17:20 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2022-05-02 9:07 Kushagra Verma
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=8cf3b100a4dc0eaac9214e1a9ea2b6dace7c85bb.camel@perches.com \
--to=joe@perches.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kushagra765@outlook.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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