From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915: Update drm/i915 bug filing URL
Date: Mon, 17 Feb 2020 11:26:09 +0200 [thread overview]
Message-ID: <874kvpwoni.fsf@intel.com> (raw)
In-Reply-To: <158158089423.11180.16774987449237829963@skylake-alporthouse-com>
On Thu, 13 Feb 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2020-02-12 16:04:34)
>> We've moved from bugzilla to gitlab.
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Hopefully the extra how-to-file-a-bug appeases Martin,
> Both,
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Thanks, both pushed.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915: Update drm/i915 bug filing URL
Date: Mon, 17 Feb 2020 11:26:09 +0200 [thread overview]
Message-ID: <874kvpwoni.fsf@intel.com> (raw)
In-Reply-To: <158158089423.11180.16774987449237829963@skylake-alporthouse-com>
On Thu, 13 Feb 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2020-02-12 16:04:34)
>> We've moved from bugzilla to gitlab.
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Hopefully the extra how-to-file-a-bug appeases Martin,
> Both,
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Thanks, both pushed.
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:[~2020-02-17 9:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 16:04 [PATCH 1/2] MAINTAINERS: Update drm/i915 bug filing URL Jani Nikula
2020-02-12 16:04 ` [Intel-gfx] " Jani Nikula
2020-02-12 16:04 ` [PATCH 2/2] drm/i915: " Jani Nikula
2020-02-12 16:04 ` [Intel-gfx] " Jani Nikula
2020-02-13 8:01 ` Chris Wilson
2020-02-13 8:01 ` Chris Wilson
2020-02-17 9:26 ` Jani Nikula [this message]
2020-02-17 9:26 ` Jani Nikula
2020-02-13 17:37 ` Sasha Levin
2020-02-13 17:37 ` [Intel-gfx] " Sasha Levin
2020-02-13 5:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] MAINTAINERS: " Patchwork
2020-02-13 17:37 ` [PATCH 1/2] " Sasha Levin
2020-02-13 17:37 ` [Intel-gfx] " Sasha Levin
2020-02-16 18:20 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] " Patchwork
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=874kvpwoni.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.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 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.