From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Uri Arev <me@wantyapps.xyz>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Len Baker" <len.baker@gmx.com>,
"Sam Ravnborg" <sam@ravnborg.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Srivathsa Dara" <srivathsa729.8@gmail.com>,
"Noralf Trønnes" <noralf@tronnes.org>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: fbtft: fix checkpatch.pl struct should normally be const
Date: Fri, 20 May 2022 08:03:44 +0200 [thread overview]
Message-ID: <YocvQJNfA8726Kf6@kroah.com> (raw)
In-Reply-To: <20220519172503.10821-1-me@wantyapps.xyz>
On Thu, May 19, 2022 at 08:25:01PM +0300, Uri Arev wrote:
> This simple patch fixes a checkpatch.pl warning in `fbtft/fbtft-core.c`.
>
> Reported by Checkpatch:
> WARNING: struct fb_ops should normally be const
>
> Signed-off-by: Uri Arev <me@wantyapps.xyz>
> ---
> drivers/staging/fbtft/fbtft-core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Always test-build your patches before submitting them :(
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Uri Arev <me@wantyapps.xyz>
Cc: "Srivathsa Dara" <srivathsa729.8@gmail.com>,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Noralf Trønnes" <noralf@tronnes.org>,
"Len Baker" <len.baker@gmx.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Sam Ravnborg" <sam@ravnborg.org>
Subject: Re: [PATCH] staging: fbtft: fix checkpatch.pl struct should normally be const
Date: Fri, 20 May 2022 08:03:44 +0200 [thread overview]
Message-ID: <YocvQJNfA8726Kf6@kroah.com> (raw)
In-Reply-To: <20220519172503.10821-1-me@wantyapps.xyz>
On Thu, May 19, 2022 at 08:25:01PM +0300, Uri Arev wrote:
> This simple patch fixes a checkpatch.pl warning in `fbtft/fbtft-core.c`.
>
> Reported by Checkpatch:
> WARNING: struct fb_ops should normally be const
>
> Signed-off-by: Uri Arev <me@wantyapps.xyz>
> ---
> drivers/staging/fbtft/fbtft-core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Always test-build your patches before submitting them :(
next prev parent reply other threads:[~2022-05-20 6:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 17:25 [PATCH] staging: fbtft: fix checkpatch.pl struct should normally be const Uri Arev
2022-05-19 17:25 ` Uri Arev
2022-05-19 17:25 ` Uri Arev
2022-05-19 20:09 ` Andy Shevchenko
2022-05-19 20:09 ` Andy Shevchenko
2022-05-19 21:25 ` kernel test robot
2022-05-19 21:25 ` kernel test robot
2022-05-20 0:41 ` kernel test robot
2022-05-20 0:41 ` kernel test robot
2022-05-20 1:34 ` kernel test robot
2022-05-20 1:34 ` kernel test robot
2022-05-20 6:03 ` Greg Kroah-Hartman [this message]
2022-05-20 6:03 ` Greg Kroah-Hartman
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=YocvQJNfA8726Kf6@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=len.baker@gmx.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=me@wantyapps.xyz \
--cc=noralf@tronnes.org \
--cc=sam@ravnborg.org \
--cc=srivathsa729.8@gmail.com \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.