From: Greg KH <gregkh@linuxfoundation.org>
To: coolrrsh@gmail.com
Cc: broonie@kernel.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH 2/2] fixes warning
Date: Fri, 4 Aug 2023 13:57:44 +0200 [thread overview]
Message-ID: <2023080435-knapsack-litter-2cbd@gregkh> (raw)
In-Reply-To: <20230804115121.34035-2-coolrrsh@gmail.com>
On Fri, Aug 04, 2023 at 05:21:21PM +0530, coolrrsh@gmail.com wrote:
> From: Rajeshwar R Shinde <coolrrsh@gmail.com>
>
> drivers/spi/spi-mpc52xx-psc.c:332:5-13:
> WARNING: Unsigned expression compared with zero: mps -> irq < 0
>
> Signed-off-by: Rajeshwar R Shinde <coolrrsh@gmail.com>
> ---
> drivers/spi/spi-mpc52xx-psc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Your subject lines are not correct :(
next prev parent reply other threads:[~2023-08-04 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 11:51 [PATCH 1/2] fixes warning coolrrsh
2023-08-04 11:51 ` [PATCH 2/2] " coolrrsh
2023-08-04 11:57 ` Greg KH [this message]
2023-08-04 11:57 ` Mark Brown
2023-08-04 11:57 ` [PATCH 1/2] " Mark Brown
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=2023080435-knapsack-litter-2cbd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=coolrrsh@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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