drm fixes for 5.3-rc9

drm fixes for 5.3-rc9

[Dave Airlie]

Hey Linus,

From the maintainer summit, just some last minute fixes for final,
details in the tag.

Dave.

drm-fixes-2019-09-13:
drm fixes for 5.3-rc9

lima:
- fix gem_wait ioctl

core:
- constify modes list

i915:
- DP MST high color depth regression
- GPU hangs on vulkan compute workloads
The following changes since commit f74c2bb98776e2de508f4d607cd519873065118e:

  Linux 5.3-rc8 (2019-09-08 13:33:15 -0700)

are available in the Git repository at:

  git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2019-09-13

for you to fetch changes up to e6bb711600db23eef2fa0c16a2d361e17b45bb28:

  Merge tag 'drm-misc-fixes-2019-09-12' of
git://anongit.freedesktop.org/drm/drm-misc into drm-fixes (2019-09-12
23:14:35 +1000)

----------------------------------------------------------------
drm fixes for 5.3-rc8

lima:
- fix gem_wait ioctl

core:
- constify modes list

i915:
- DP MST high color depth regression
- GPU hangs on vulkan compute workloads

----------------------------------------------------------------
Chris Wilson (1):
      drm/i915: Restore relaxed padding (OCL_OOB_SUPPRES_ENABLE) for skl+

Dave Airlie (2):
      Merge tag 'drm-intel-fixes-2019-09-11' of
git://anongit.freedesktop.org/drm/drm-intel into drm-fixes
      Merge tag 'drm-misc-fixes-2019-09-12' of
git://anongit.freedesktop.org/drm/drm-misc into drm-fixes

Maxime Ripard (1):
      drm/modes: Make the whitelist more const

Vasily Khoruzhick (1):
      drm/lima: fix lima_gem_wait() return value

Ville Syrjälä (1):
      drm/i915: Limit MST to <= 8bpc once again

 drivers/gpu/drm/drm_modes.c                 |  2 +-
 drivers/gpu/drm/i915/display/intel_dp_mst.c | 10 +++++++++-
 drivers/gpu/drm/i915/gt/intel_workarounds.c |  5 -----
 drivers/gpu/drm/lima/lima_gem.c             |  2 +-
 4 files changed, 11 insertions(+), 8 deletions(-)

Re: drm fixes for 5.3-rc9

[Linus Torvalds]

On Thu, Sep 12, 2019 at 8:56 AM Dave Airlie <airlied@gmail.com> wrote:
>
> Hey Linus,
>
> From the maintainer summit, just some last minute fixes for final,
> details in the tag.

So because my mailbox was more unruly than normal (because of same
maintainer summit travel), I almost missed this email entirely.

Why? Because you don't have the normal "git pull" anywhere in the
email, so it doesn't trigger my search for important emails.

There's a "git" in the email body, but there's not a "pull" anywhere.
Could you add either a "please pull" or something to the email body -
or to make things _really_ obvious, add the "[GIT PULL]" prefix to the
subject line? Or anything, really, to whatever script or workflow you
use to generate these?

             Linus

Re: drm fixes for 5.3-rc9

[Dave Airlie]

On Sun, 15 Sep 2019 at 04:58, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Thu, Sep 12, 2019 at 8:56 AM Dave Airlie <airlied@gmail.com> wrote:
> >
> > Hey Linus,
> >
> > From the maintainer summit, just some last minute fixes for final,
> > details in the tag.
>
> So because my mailbox was more unruly than normal (because of same
> maintainer summit travel), I almost missed this email entirely.
>
> Why? Because you don't have the normal "git pull" anywhere in the
> email, so it doesn't trigger my search for important emails.
>
> There's a "git" in the email body, but there's not a "pull" anywhere.
> Could you add either a "please pull" or something to the email body -
> or to make things _really_ obvious, add the "[GIT PULL]" prefix to the
> subject line? Or anything, really, to whatever script or workflow you
> use to generate these?

I've been manually writing the subject lines, seems I need to fix my brain.

The reason I do that is I generate on one machine the body, and send
it via the gmail webui on whatever machine I'm using. This helps
avoids google tagging my emails as spam for generating them using
someone elses smtp servers. I should probably setup properly sending
gmail to avoid that.

Dave.

Re: drm fixes for 5.3-rc9

[Linus Torvalds]

On Sun, Sep 15, 2019 at 8:12 AM Dave Airlie <airlied@gmail.com> wrote:
>
> I've been manually writing the subject lines, seems I need to fix my brain.

Note that my "find git pull requests" logic doesn't need it in the
subject line at all, so if you just change whatever script you use to
generate the email body to have an additional "pull" in there
somewhere, that's perfectly workable too.

> The reason I do that is I generate on one machine the body, and send
> it via the gmail webui on whatever machine I'm using. This helps
> avoids google tagging my emails as spam for generating them using
> someone elses smtp servers. I should probably setup properly sending
> gmail to avoid that.

Don't worry too much about it too much.

I _do_ try to always read all my email, it's just that I find things
faster that match that pattern.

And I don't think I've actually lost one of your pull requests (knock
wood), they might just end up delayed a bit.

That said - having "[GIT PULL]" in the subject line is how the
pr-tracker-bot finds the emails too, so if you do the subject line
thing, you'll not only trigger my search term, you'll also get the
nice notifications from the bot when I've pushed out my merge.

              Linus