From: Jani Nikula <jani.nikula@intel.com>
To: Francesco Poli <invernomuto@paranoici.org>, imre.deak@intel.com
Cc: Intel GFX list <intel-gfx@lists.freedesktop.org>,
1075770@bugs.debian.org
Subject: Re: [bug report] adlp_tc_phy_connect [i915] floods logs with drm_WARN_ON(tc->mode == TC_PORT_LEGACY) call traces
Date: Mon, 29 Jul 2024 13:19:06 +0300 [thread overview]
Message-ID: <87v80oxzz9.fsf@intel.com> (raw)
In-Reply-To: <20240725235929.68dd56625806ac0c8d20a2c8@paranoici.org>
On Thu, 25 Jul 2024, Francesco Poli <invernomuto@paranoici.org> wrote:
> I had reported the bug to the Debian BTS (Bug Tracking System), where
> I was told to report the bug upstream, by contacting developers/mailing
> lists.
> Now on this mailing list, I am being told to report the issue on
> gitlab.freedesktop.org (which requires to register an account, in order
> to report issues)... Having to jump through all these hoops is beginning
> to be a little time consuming... :-(
There are a number of reasons why email and mailing lists are really bad
for reporting bugs, from our perspective, which is why we've asked
people to report bugs to freedesktop.org bug trackers for about a decade
now.
If the right person doesn't have time to resolve the issue right away,
it'll likely be forgotten on the mailing list. Attachments aren't
welcome on mailing lists, let alone big logs. It's easier to label and
reference issues on a bug tracker. It's easier (yes, for us) to manage
the issues, and the people working on them, on a bug tracker. And so on.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-07-29 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 18:35 [bug report] adlp_tc_phy_connect [i915] floods logs with drm_WARN_ON(tc->mode == TC_PORT_LEGACY) call traces Francesco Poli
2024-07-24 16:02 ` Jani Nikula
2024-07-24 16:03 ` Jani Nikula
2024-07-24 18:40 ` Imre Deak
2024-07-24 18:30 ` Imre Deak
2024-07-25 21:59 ` Francesco Poli
2024-07-29 10:19 ` Jani Nikula [this message]
2024-10-29 7:47 ` Francesco Poli
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=87v80oxzz9.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=1075770@bugs.debian.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=invernomuto@paranoici.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).