All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ander Conselvan De Oliveira <conselvan2@gmail.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: Adding custom bugzilla fields
Date: Fri, 21 Aug 2015 11:41:45 +0300	[thread overview]
Message-ID: <87io89av92.fsf@intel.com> (raw)
In-Reply-To: <1435666457.2771.12.camel@gmail.com>

On Tue, 30 Jun 2015, Ander Conselvan De Oliveira <conselvan2@gmail.com> wrote:
> On Mon, 2015-06-29 at 14:31 +0300, Ander Conselvan De Oliveira wrote:
>> On Fri, 2015-06-26 at 18:28 +0300, Ander Conselvan De Oliveira wrote:
>> > Hi all,
>> > 
>> > I've been looking into creating custom fields in Bugzilla to help sort
>> > our bugs in a more manageable way.
>> 
>> [...]
>> 
>> > So I would like to hear what other people think about this. Specially,
>> > about what should be in the features field. The values can change
>> > overtime, but would be good to have a good list from the start.
>> 
>> So here's the list after including Daniel's and Ville's feedback. If
>> there's no more suggestions/objections, I'd like to create those fields
>> already tomorrow. We can edit the list entries afterwards if needed.
>
> Thank you, everyone, for the input. The fields are now created.

There are some additional feature fields that I've found might be
useful:

display/adapter (or display/dongle?)
display/hotplug
display/multi-gpu
GEM/prime (or GEM/dma-buf?)

other/IOMMU (or GEM/IOMMU?)
other/BIOS
other/module-reload (?)

performance?


BR,
Jani.



-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-08-21  8:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 15:28 Adding custom bugzilla fields Ander Conselvan De Oliveira
2015-06-26 17:05 ` Daniel Vetter
2015-06-26 17:23   ` Chris Wilson
2015-06-26 17:34     ` Daniel Vetter
2015-06-29  7:42     ` Jani Nikula
2015-06-29  8:50   ` Ander Conselvan De Oliveira
2015-06-29 10:19     ` Ville Syrjälä
2015-06-29 10:26       ` Ville Syrjälä
2015-06-29 11:20         ` Ander Conselvan De Oliveira
2015-06-29 11:31 ` Ander Conselvan De Oliveira
2015-06-29 11:34   ` Chris Wilson
2015-06-29 11:46     ` Ander Conselvan De Oliveira
2015-06-29 11:47   ` Jani Nikula
2015-06-29 11:59     ` Ander Conselvan De Oliveira
2015-06-29 16:31   ` Daniel Vetter
2015-06-29 20:11     ` Chris Wilson
2015-06-30 10:05       ` Daniel Vetter
2015-06-30 10:07         ` Chris Wilson
2015-06-30 10:13           ` Chris Wilson
2015-06-30 12:14   ` Ander Conselvan De Oliveira
2015-08-21  8:41     ` Jani Nikula [this message]
2015-08-25 12:49       ` Daniel Vetter
2015-08-25 15:20         ` Jani Nikula
2015-08-28  6:50         ` 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=87io89av92.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=conselvan2@gmail.com \
    --cc=intel-gfx@lists.freedesktop.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.