From: Javier Martinez Canillas <javierm@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v1 2/2] firmware: sysfb: Don't use "proxy" headers
Date: Fri, 27 Jun 2025 10:51:07 +0200 [thread overview]
Message-ID: <87frfld0uc.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <20250626172039.329052-3-andriy.shevchenko@linux.intel.com>
Andy Shevchenko <andriy.shevchenko@linux.intel.com> writes:
> Update header inclusions to follow IWYU (Include What You Use)
> principle.
>
> Note that kernel.h is discouraged to be included as it's written
> at the top of that file.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2025-06-27 8:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 17:18 [PATCH v1 0/2] firmware: sysfb: Unorphan and fix header Andy Shevchenko
2025-06-26 17:19 ` [PATCH v1 1/2] firmware: sysfb: Unorphan sysfb files Andy Shevchenko
2025-06-27 8:50 ` Javier Martinez Canillas
2025-06-27 9:02 ` Andy Shevchenko
2025-06-27 9:19 ` Javier Martinez Canillas
2025-06-27 10:22 ` Andy Shevchenko
2025-06-27 10:33 ` Javier Martinez Canillas
2025-06-27 10:50 ` Andy Shevchenko
2025-06-27 11:37 ` Javier Martinez Canillas
2025-06-26 17:19 ` [PATCH v1 2/2] firmware: sysfb: Don't use "proxy" headers Andy Shevchenko
2025-06-27 8:51 ` Javier Martinez Canillas [this message]
2025-06-27 10:35 ` Andy Shevchenko
2025-06-27 8:38 ` [PATCH v1 0/2] firmware: sysfb: Unorphan and fix header Thomas Zimmermann
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=87frfld0uc.fsf@minerva.mail-host-address-is-not-set \
--to=javierm@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.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 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).