From: Jani Nikula <jani.nikula@intel.com>
To: Lyude Paul <lyude@redhat.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/dp: start using more of the extended receiver caps
Date: Mon, 21 Sep 2020 21:37:06 +0300 [thread overview]
Message-ID: <87v9g7q8ml.fsf@intel.com> (raw)
In-Reply-To: <3df7f6ec13348537bec5e0736563616e9ed05c28.camel@redhat.com>
On Mon, 21 Sep 2020, Lyude Paul <lyude@redhat.com> wrote:
> On Tue, 2020-09-01 at 21:01 +0300, Jani Nikula wrote:
>> I guess we can try without the change, and fix later if we hit issues.
>
> I'm fine with the change if it doesn't break things btw - just as long as
> we're making sure that we don't zero things out by accident
My conclusion was to go without, it's a trivial change to add
afterwards as needed.
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
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@intel.com>
To: Lyude Paul <lyude@redhat.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/dp: start using more of the extended receiver caps
Date: Mon, 21 Sep 2020 21:37:06 +0300 [thread overview]
Message-ID: <87v9g7q8ml.fsf@intel.com> (raw)
In-Reply-To: <3df7f6ec13348537bec5e0736563616e9ed05c28.camel@redhat.com>
On Mon, 21 Sep 2020, Lyude Paul <lyude@redhat.com> wrote:
> On Tue, 2020-09-01 at 21:01 +0300, Jani Nikula wrote:
>> I guess we can try without the change, and fix later if we hit issues.
>
> I'm fine with the change if it doesn't break things btw - just as long as
> we're making sure that we don't zero things out by accident
My conclusion was to go without, it's a trivial change to add
afterwards as needed.
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
next prev parent reply other threads:[~2020-09-21 18:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 12:32 [Intel-gfx] [PATCH] drm/dp: start using more of the extended receiver caps Jani Nikula
2020-09-01 12:32 ` Jani Nikula
2020-09-01 13:03 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2020-09-01 17:48 ` [Intel-gfx] [PATCH] " Lyude Paul
2020-09-01 17:48 ` Lyude Paul
2020-09-01 18:01 ` [Intel-gfx] " Jani Nikula
2020-09-01 18:01 ` Jani Nikula
2020-09-21 18:13 ` [Intel-gfx] " Lyude Paul
2020-09-21 18:13 ` Lyude Paul
2020-09-21 18:37 ` Jani Nikula [this message]
2020-09-21 18:37 ` 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=87v9g7q8ml.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--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 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.