From: Jani Nikula <jani.nikula@linux.intel.com>
To: Werner Sembach <wse@tuxedocomputers.com>,
wse@tuxedocomputers.com, ville.syrjala@linux.intel.com,
airlied@linux.ie, daniel@ffwll.ch,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 1/3] New function to avoid duplicate code in upcomming commits
Date: Thu, 06 May 2021 13:21:08 +0300 [thread overview]
Message-ID: <87pmy4w4bv.fsf@intel.com> (raw)
In-Reply-To: <20210505172401.1453178-2-wse@tuxedocomputers.com>
On Wed, 05 May 2021, Werner Sembach <wse@tuxedocomputers.com> wrote:
> Subject: [PATCH 1/3] New function to avoid duplicate code in upcomming commits
Also, the subject should have a prefix, such as "drm/i915/hdmi: "
etc. depending on what you're changing. See git log on the files for
examples.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Werner Sembach <wse@tuxedocomputers.com>,
wse@tuxedocomputers.com, ville.syrjala@linux.intel.com,
airlied@linux.ie, daniel@ffwll.ch,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 1/3] New function to avoid duplicate code in upcomming commits
Date: Thu, 06 May 2021 13:21:08 +0300 [thread overview]
Message-ID: <87pmy4w4bv.fsf@intel.com> (raw)
In-Reply-To: <20210505172401.1453178-2-wse@tuxedocomputers.com>
On Wed, 05 May 2021, Werner Sembach <wse@tuxedocomputers.com> wrote:
> Subject: [PATCH 1/3] New function to avoid duplicate code in upcomming commits
Also, the subject should have a prefix, such as "drm/i915/hdmi: "
etc. depending on what you're changing. See git log on the files for
examples.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-05-06 10:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 17:23 [PATCH 0/3] drm/i915/display Try YCbCr420 color when RGB fails Werner Sembach
2021-05-05 17:23 ` [Intel-gfx] " Werner Sembach
2021-05-05 17:23 ` Werner Sembach
2021-05-05 17:23 ` [PATCH 1/3] New function to avoid duplicate code in upcomming commits Werner Sembach
2021-05-05 17:23 ` [Intel-gfx] " Werner Sembach
2021-05-05 17:23 ` Werner Sembach
2021-05-06 10:19 ` [Intel-gfx] " Jani Nikula
2021-05-06 10:19 ` Jani Nikula
2021-05-06 16:41 ` Werner Sembach
2021-05-06 16:41 ` Werner Sembach
2021-05-06 16:41 ` Werner Sembach
2021-05-06 17:33 ` Jani Nikula
2021-05-06 17:33 ` Jani Nikula
2021-05-06 10:21 ` Jani Nikula [this message]
2021-05-06 10:21 ` Jani Nikula
2021-05-05 17:24 ` [PATCH 2/3] Restructure output format computation for better expandability Werner Sembach
2021-05-05 17:24 ` [Intel-gfx] " Werner Sembach
2021-05-05 17:24 ` Werner Sembach
2021-05-05 17:24 ` [PATCH 3/3] Use YCbCr420 as fallback when RGB fails Werner Sembach
2021-05-05 17:24 ` [Intel-gfx] " Werner Sembach
2021-05-05 17:24 ` Werner Sembach
2021-05-05 17:25 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/display Try YCbCr420 color " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-05-05 17:14 [PATCH 0/3] " Werner Sembach
2021-05-05 17:14 ` [Intel-gfx] [PATCH 1/3] New function to avoid duplicate code in upcomming commits Werner Sembach
2021-05-05 14:10 [PATCH 0/4] drm/i915/display Try YCbCr420 color when RGB fails Werner Sembach
2021-05-05 14:10 ` [Intel-gfx] [PATCH 1/3] New function to avoid duplicate code in upcomming commits Werner Sembach
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=87pmy4w4bv.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ville.syrjala@linux.intel.com \
--cc=wse@tuxedocomputers.com \
/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.