From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>,
"Syrjala, Ville" <ville.syrjala@linux.intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Mika Kahola <mika.kahola@intel.com>,
Ander Conselvan de Oliveira
<ander.conselvan.de.oliveira@intel.com>,
"Deak, Imre" <imre.deak@intel.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Matthew D Roper <matthew.d.roper@intel.com>,
"Lespiau, Damien" <damien.lespiau@intel.com>
Subject: Re: drm-intel.git Committers: Reminder about tagging bugfixes
Date: Mon, 01 Aug 2016 14:54:40 +0300 [thread overview]
Message-ID: <878twgvh4v.fsf@intel.com> (raw)
In-Reply-To: <CAKMK7uH95ohtUz9EqRRBhS14SAE-jhh037KQUYcpdc1yD4O8_w@mail.gmail.com>
On Thu, 14 Jul 2016, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> Hi all,
>
> Apparently this wasn't known to everyone, hence this small reminder
> about correctly tagging bugfixes when pushing them:
> - add a Bugzilla: or References: link for any bug reported anywhere
> (bugzilla or mailing list). Also add Reported-by:/Tested-by: for
> credits.
FWIW, greping git logs says we should prefer "Reference:" over
"References:".
BR,
Jani.
> - add Fixes: if it's a regression fix. Run "dim fixes $sha1" for
> convenience, to generate this correctly
> - add correct Cc: tags, Cc: stable for backporting to all kernels
> (including -rc), Cc: drm-intel-fixes if it's only needed in current
> -rc series.
>
> Special note about pre-production hw: We only backport fixes when the
> prelim_hw_support tag is lifted, before that point we don't bother.
> But after that _all_ bugfixes need one of the above tags, and right
> now both kbl and apl/bxt aren't preliminary any more!
>
> For full details see the docs:
> https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-intel.html
> If you haven't read them in a while would be good to check them out
> again, quite a few improvements and clarifications over the past few
> months.
>
> Thanks, Daniel
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-08-01 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 12:20 drm-intel.git Committers: Reminder about tagging bugfixes Daniel Vetter
2016-08-01 11:54 ` 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=878twgvh4v.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=damien.lespiau@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.d.roper@intel.com \
--cc=mika.kahola@intel.com \
--cc=paulo.r.zanoni@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=ville.syrjala@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox