On Sat, Sep 04, 2021 at 12:01:27PM +0530, srivathsa wrote: > Signed-off-by: Srivathsa Dara <srivathsa729.8@xxxxxxxxx> > --- > drivers/staging/fbtft/fbtft-core.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/staging/fbtft/fbtft-core.c b/drivers/staging/fbtft/fbtft-core.c > index ed992ca605eb..65de1c02e7dc 100644 > --- a/drivers/staging/fbtft/fbtft-core.c > +++ b/drivers/staging/fbtft/fbtft-core.c > @@ -1038,7 +1038,8 @@ int fbtft_init_display(struct fbtft_par *par) > i++; > > /* make debug message */ > - for (j = 0; par->init_sequence[i + 1 + j] >= 0; j++); > + for (j = 0; par->init_sequence[i + 1 + j] >= 0; j++) > + ; > > fbtft_par_dbg(DEBUG_INIT_DISPLAY, par, > "init: write(0x%02X) %*ph\n", > -- > 2.25.1 > > 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: - You did not specify a description of why the patch is needed, or possibly, any description at all, in the email body. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/SubmittingPatches for what is needed in order to properly describe the change. - You did not write a descriptive Subject: for the patch, allowing Greg, and everyone else, to know what this patch is all about. Please read the section entitled "The canonical patch format" in the kernel file, Documentation/SubmittingPatches for what a proper Subject: line should look like. If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers. thanks, greg k-h's patch email bot
