All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Adding custom bugzilla fields
Date: Fri, 28 Aug 2015 09:50:22 +0300	[thread overview]
Message-ID: <87egin7vpt.fsf@intel.com> (raw)
In-Reply-To: <20150825124920.GF20434@phenom.ffwll.local>

On Tue, 25 Aug 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Fri, Aug 21, 2015 at 11:41:45AM +0300, Jani Nikula wrote:
>> 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:

The discussion yesterday never materialized, so I'll reply here.

>> display/adapter (or display/dongle?)
> display/DP?

This does not answer the question "I want to see all our adapter bugs".

>> display/hotplug
> tag it with relevant output port?

This does not answer the question "I want to see all our hotplug bugs".

>> display/multi-gpu
>> GEM/prime (or GEM/dma-buf?)
>
> Yeah this might be useful, but not sure how much we care.

I might continue like above, because it's useful for finding dupes, but
also it's nice to flag bugs we're not sure how much we care. If they end
up being flagged, say, DP because gpu switching affects that, it's still
a useful distinction to know it's not your average DP bug.

>> other/IOMMU (or GEM/IOMMU?)
>> other/BIOS
>
> Imo better to label with relevant feature that gets broken.

This does not answer the question "I want to see all our bugs related to
VBT/BIOS screwups".

> And IOMMU should always have dwmw on cc so he can escalate.

That is totally irrelevant to the discussion about fields.

>> other/module-reload (?)
>
> This is BAT now and should never break ;-)

Fine.

>> performance?
>
> Yeah this would be good I guess.
>
> In general I'm vary of adding too many since it'll be hard to maintain.

Don't worry, we can remove them too.

> Can you please join the bug scrub org mtg on Thu so we can discuss these?
>
> Thanks, Daniel
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch

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

      parent reply	other threads:[~2015-08-28  6:47 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
2015-08-25 12:49       ` Daniel Vetter
2015-08-25 15:20         ` Jani Nikula
2015-08-28  6:50         ` 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=87egin7vpt.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --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.