From: Andi Shyti <andi.shyti@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Xinliang Liu <xinliang.liu@linaro.org>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Xinwei Kong <kong.kongxinwei@hisilicon.com>,
Yongqin Liu <yongqin.liu@linaro.org>,
Tian Tao <tiantao6@hisilicon.com>,
John Stultz <jstultz@google.com>,
Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: [PATCH 2/3] drm/hisilicon: include drm/drm_edid.h only where needed
Date: Fri, 5 Jan 2024 10:59:56 +0100 [thread overview]
Message-ID: <ZZfTHAbysZnBlvrg@ashyti-mobl2.lan> (raw)
In-Reply-To: <20240104201632.1100753-2-jani.nikula@intel.com>
Hi Jani,
On Thu, Jan 04, 2024 at 10:16:31PM +0200, Jani Nikula wrote:
> Reduce the need for rebuilds when drm_edid.h is modified by including it
> only where needed.
>
> Cc: Xinliang Liu <xinliang.liu@linaro.org>
> Cc: Tian Tao <tiantao6@hisilicon.com>
> Cc: Xinwei Kong <kong.kongxinwei@hisilicon.com>
> Cc: Sumit Semwal <sumit.semwal@linaro.org>
> Cc: Yongqin Liu <yongqin.liu@linaro.org>
> Cc: John Stultz <jstultz@google.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Andi
next prev parent reply other threads:[~2024-01-05 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 20:16 [PATCH 1/3] drm/nouveau: include drm/drm_edid.h only where needed Jani Nikula
2024-01-04 20:16 ` [PATCH 2/3] drm/hisilicon: " Jani Nikula
2024-01-05 9:59 ` Andi Shyti [this message]
2024-01-04 20:16 ` [PATCH 3/3] ASoC: hdmi-codec: drop drm/drm_edid.h include Jani Nikula
2024-01-05 10:05 ` Andi Shyti
2024-01-05 16:04 ` Alex Deucher
2024-01-10 9:24 ` Jani Nikula
2024-01-12 13:26 ` [3/3] " Sarha, Jyri
2024-01-16 16:14 ` Jani Nikula
2024-01-04 23:28 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/nouveau: include drm/drm_edid.h only where needed Patchwork
2024-01-05 1:16 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-01-05 9:59 ` [PATCH 1/3] " Andi Shyti
2024-01-08 18:04 ` Danilo Krummrich
2024-01-09 9:59 ` Jani Nikula
2024-01-09 17:01 ` Danilo Krummrich
2024-01-10 9:18 ` Jani Nikula
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=ZZfTHAbysZnBlvrg@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jstultz@google.com \
--cc=kong.kongxinwei@hisilicon.com \
--cc=sumit.semwal@linaro.org \
--cc=tiantao6@hisilicon.com \
--cc=xinliang.liu@linaro.org \
--cc=yongqin.liu@linaro.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