All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Melissa Wen <mwen@igalia.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH v1 1/1] drm: fixed: Don't use "proxy" headers
Date: Tue, 13 Aug 2024 13:25:36 +0300	[thread overview]
Message-ID: <87zfpgzplr.fsf@intel.com> (raw)
In-Reply-To: <ZrscJvDZqMQNFgR3@smile.fi.intel.com>

On Tue, 13 Aug 2024, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> On Thu, Apr 25, 2024 at 08:12:33PM +0300, Andy Shevchenko wrote:
>> On Mon, Apr 22, 2024 at 09:49:04PM +0300, Jani Nikula wrote:
>> > On Mon, 22 Apr 2024, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
>> > > Update header inclusions to follow IWYU (Include What You Use)
>> > > principle.
>> > >
>> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> > 
>> > Assuming it builds, and nothing depends on other stuff from kernel.h via
>> > drm_fixed.h,
>> 
>> For the record, I have built-tested this via `make allyesconfig` on x86_64.
>> 
>> > Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>> 
>> Thank you!
>
> Who is going to apply this, please?

Pushed to drm-misc-next, thanks for the patch.

BR,
Jani.

-- 
Jani Nikula, Intel

      reply	other threads:[~2024-08-13 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 14:33 [PATCH v1 1/1] drm: fixed: Don't use "proxy" headers Andy Shevchenko
2024-04-22 18:49 ` Jani Nikula
2024-04-25 17:12   ` Andy Shevchenko
2024-08-13  8:41     ` Andy Shevchenko
2024-08-13 10:25       ` Jani Nikula [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=87zfpgzplr.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=mwen@igalia.com \
    --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 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.