From: "Hennerich, Michael" <Michael.Hennerich@analog.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Helge Deller <deller@gmx.de>
Subject: RE: [PATCH v1 1/1] fbtft: seps525: Don't use "proxy" headers
Date: Sat, 27 Apr 2024 00:33:42 +0000 [thread overview]
Message-ID: <CO3PR03MB6774B71BE189707726C8E7928E152@CO3PR03MB6774.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20240423173623.2748621-1-andriy.shevchenko@linux.intel.com>
> -----Original Message-----
> From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Sent: Tuesday, April 23, 2024 1:36 PM
> To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>; linux-
> fbdev@vger.kernel.org; dri-devel@lists.freedesktop.org; linux-
> staging@lists.linux.dev; linux-kernel@vger.kernel.org
> Cc: Hennerich, Michael <Michael.Hennerich@analog.com>; Greg Kroah-
> Hartman <gregkh@linuxfoundation.org>; Helge Deller <deller@gmx.de>
> Subject: [PATCH v1 1/1] fbtft: seps525: Don't use "proxy" headers
>
> Update header inclusions to follow IWYU (Include What You Use) principle.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: Michael Hennerich <michael.hennerich@analog.com>
> ---
> drivers/staging/fbtft/fb_seps525.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/fbtft/fb_seps525.c
> b/drivers/staging/fbtft/fb_seps525.c
> index 05882e2cde7f..46c257308b49 100644
> --- a/drivers/staging/fbtft/fb_seps525.c
> +++ b/drivers/staging/fbtft/fb_seps525.c
> @@ -16,11 +16,10 @@
> * GNU General Public License for more details.
> */
>
> -#include <linux/module.h>
> -#include <linux/kernel.h>
> -#include <linux/init.h>
> -#include <linux/gpio.h>
> +#include <linux/bits.h>
> #include <linux/delay.h>
> +#include <linux/init.h>
> +#include <linux/module.h>
>
> #include "fbtft.h"
>
> --
> 2.43.0.rc1.1336.g36b5255a03ac
prev parent reply other threads:[~2024-04-27 3:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 17:36 [PATCH v1 1/1] fbtft: seps525: Don't use "proxy" headers Andy Shevchenko
2024-04-27 0:33 ` Hennerich, Michael [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=CO3PR03MB6774B71BE189707726C8E7928E152@CO3PR03MB6774.namprd03.prod.outlook.com \
--to=michael.hennerich@analog.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).