From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Dimitri Sivanich <dimitri.sivanich@hpe.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2] misc: sgi-gru: use explicitly signed char
Date: Tue, 25 Oct 2022 14:10:50 +0200 [thread overview]
Message-ID: <Y1fSSt17uXy/YP1D@zx2c4.com> (raw)
In-Reply-To: <Y1eShe+T8YTiokN5@kroah.com>
On Tue, Oct 25, 2022 at 09:38:45AM +0200, Greg Kroah-Hartman wrote:
> On Tue, Oct 25, 2022 at 04:52:23AM +0200, Jason A. Donenfeld wrote:
> > With char becoming unsigned by default, and with `char` alone being
> > ambiguous and based on architecture, signed chars need to be marked
> > explicitly as such. This fixes warnings like:
> >
> > drivers/misc/sgi-gru/grumain.c:711 gru_check_chiplet_assignment() warn: 'gts->ts_user_chiplet_id' is unsigned
> >
> > Cc: Dimitri Sivanich <dimitri.sivanich@hpe.com>
> > Cc: Arnd Bergmann <arnd@arndb.de>
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> > ---
> > drivers/misc/sgi-gru/grumain.c | 6 +++---
> > drivers/misc/sgi-gru/grutables.h | 14 +++++++-------
> > 2 files changed, 10 insertions(+), 10 deletions(-)
>
> 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:
>
> - This looks like a new version of a previously submitted patch, but you
> did not list below the --- line any changes from the previous version.
> Please read the section entitled "The canonical patch format" in the
> kernel file, Documentation/SubmittingPatches for what needs to be done
> here to properly describe this.
I fixed the kbuild errors that v2 was a reply to. Specifically, I fixed
up the function prototypes in grutables.h.
Jason
prev parent reply other threads:[~2022-10-25 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 16:28 [PATCH] " Jason A. Donenfeld
2022-10-25 2:37 ` kernel test robot
2022-10-25 2:52 ` [PATCH v2] " Jason A. Donenfeld
2022-10-25 7:38 ` Greg Kroah-Hartman
2022-10-25 12:10 ` Jason A. Donenfeld [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=Y1fSSt17uXy/YP1D@zx2c4.com \
--to=jason@zx2c4.com \
--cc=arnd@arndb.de \
--cc=dimitri.sivanich@hpe.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
Powered by JetHome