From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Cornij\, Nikola" <Nikola.Cornij@amd.com>,
"lyude\@redhat.com" <lyude@redhat.com>,
"amd-gfx\@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"koba.ko@canonical.com" <koba.ko@canonical.com>,
"Pillai, Aurabindo" <Aurabindo.Pillai@amd.com>,
"bskeggs@redhat.com" <bskeggs@redhat.com>,
"Lipski, Mikita" <Mikita.Lipski@amd.com>
Subject: RE: [PATCH v2 1/1] drm/i915: Use the correct max source link rate for MST
Date: Mon, 03 May 2021 11:44:41 +0300 [thread overview]
Message-ID: <87h7jk1a12.fsf@intel.com> (raw)
In-Reply-To: <DM5PR12MB4679215F5490F2D38E2A6C51EE5E9@DM5PR12MB4679.namprd12.prod.outlook.com>
On Fri, 30 Apr 2021, "Cornij, Nikola" <Nikola.Cornij@amd.com> wrote:
> I'll fix the dpcd part to use kHz on Monday
I'd appreciate that, thanks. I think it is the better interface.
> My apologies as well, not only for coming up with the wrong patch in
> first place, but also for missing to CC all the maintainers.
The drivers we have are monsters, and it can be tricky to get the
details right. All the more important to get the Cc's right; then at
least you can blame us afterwards. ;)
Thanks for reacting quickly, though.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2021-05-03 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 21:45 [PATCH v2 0/1] drm/i915: Use the correct max source link rate for MST Nikola Cornij
2021-04-30 21:45 ` [PATCH v2 1/1] " Nikola Cornij
2021-04-30 22:41 ` Lyude Paul
2021-04-30 22:55 ` Cornij, Nikola
2021-05-03 8:44 ` 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=87h7jk1a12.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Aurabindo.Pillai@amd.com \
--cc=Mikita.Lipski@amd.com \
--cc=Nikola.Cornij@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=koba.ko@canonical.com \
--cc=lyude@redhat.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;
as well as URLs for NNTP newsgroup(s).