From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Helge Deller <deller@gmx.de>
Subject: Re: [PATCH v1 1/1] staging: fbtft: Consider type of init sequence values in fbtft_init_display()
Date: Tue, 8 Mar 2022 12:18:25 +0200 [thread overview]
Message-ID: <Yictcf0BCvveVT+V@smile.fi.intel.com> (raw)
In-Reply-To: <20220304193414.88006-1-andriy.shevchenko@linux.intel.com>
+Cc: Helge
Maybe you can pick this up?
On Fri, Mar 04, 2022 at 09:34:14PM +0200, Andy Shevchenko wrote:
> In the fbtft_init_display() the init sequence is printed for
> the debug purposes. Unfortunately the current code doesn't take
> into account that values in the buffer are of the s16 type.
>
> Consider that and replace the printing code with fbtft_par_dbg_hex()
> call.
>
> Fixes: b888897014a9 ("staging/fbtft: Remove all strcpy() uses")
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> drivers/staging/fbtft/fbtft-core.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/fbtft/fbtft-core.c b/drivers/staging/fbtft/fbtft-core.c
> index 4a35347b3020..b28a059ad3b4 100644
> --- a/drivers/staging/fbtft/fbtft-core.c
> +++ b/drivers/staging/fbtft/fbtft-core.c
> @@ -1035,10 +1035,9 @@ int fbtft_init_display(struct fbtft_par *par)
> for (j = 0; par->init_sequence[i + 1 + j] >= 0; j++)
> ;
>
> - fbtft_par_dbg(DEBUG_INIT_DISPLAY, par,
> - "init: write(0x%02X) %*ph\n",
> - par->init_sequence[i], j,
> - &par->init_sequence[i + 1]);
> + fbtft_par_dbg_hex(DEBUG_INIT_DISPLAY, par, par->info->device,
> + s16, &par->init_sequence[i + 1], j,
> + "init: write(0x%02X)", par->init_sequence[i]);
>
> /* Write */
> j = 0;
> --
> 2.34.1
>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-03-08 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 19:34 [PATCH v1 1/1] staging: fbtft: Consider type of init sequence values in fbtft_init_display() Andy Shevchenko
2022-03-08 10:18 ` Andy Shevchenko [this message]
2022-03-08 10:46 ` Greg Kroah-Hartman
2022-03-08 12:13 ` Andy Shevchenko
2022-03-14 17:28 ` Greg Kroah-Hartman
2022-03-16 16:51 ` Andy Shevchenko
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=Yictcf0BCvveVT+V@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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