From: Jani Nikula <jani.nikula@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
tglx@linutronix.de, x86@kernel.org, tj@kernel.org,
peterz@infradead.org, mathieu.desnoyers@efficios.com,
paulmck@kernel.org, keescook@chromium.org,
dave.hansen@linux.intel.com, mingo@redhat.com, will@kernel.org,
longman@redhat.com, boqun.feng@gmail.com, brauner@kernel.org,
intel-gfx@lists.freedesktop.org, Dave Airlie <airlied@redhat.com>,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH 01/50] drivers/gpu/drm/i915/i915_memcpy.c: fix missing includes
Date: Fri, 08 Mar 2024 15:46:10 +0200 [thread overview]
Message-ID: <8734t0vntp.fsf@intel.com> (raw)
In-Reply-To: <20231216024834.3510073-2-kent.overstreet@linux.dev>
On Fri, 15 Dec 2023, Kent Overstreet <kent.overstreet@linux.dev> wrote:
> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
This seems to have been merged to v6.8-rc1 as commit 86b9357c1bbe
("drivers/gpu/drm/i915/i915_memcpy.c: fix missing includes") without
Cc'ing the relevant lists or people, with no commit message or reviews,
or the CI we mandate for every single patch.
Sure it's trivial, but please extend the same courtesy to us as you'd
expect everyone else to extend to you before just merging stuff in the
trees you maintain.
Thanks,
Jani.
> ---
> drivers/gpu/drm/i915/i915_memcpy.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_memcpy.c b/drivers/gpu/drm/i915/i915_memcpy.c
> index 1b021a4902de..40b288136841 100644
> --- a/drivers/gpu/drm/i915/i915_memcpy.c
> +++ b/drivers/gpu/drm/i915/i915_memcpy.c
> @@ -23,6 +23,8 @@
> */
>
> #include <linux/kernel.h>
> +#include <linux/string.h>
> +#include <asm/cpufeature.h>
> #include <asm/fpu/api.h>
>
> #include "i915_memcpy.h"
--
Jani Nikula, Intel
parent reply other threads:[~2024-03-08 13:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20231216024834.3510073-2-kent.overstreet@linux.dev>]
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=8734t0vntp.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@redhat.com \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dave.hansen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keescook@chromium.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=will@kernel.org \
--cc=x86@kernel.org \
/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