From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dim-tools@lists.freedesktop.org,
Maxime Ripard <maxime.ripard@bootlin.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [PULL] drm-fixes
Date: Fri, 21 Dec 2018 14:39:58 +0100 [thread overview]
Message-ID: <20181221133958.GA24222@phenom.ffwll.local> (raw)
Hi Linus,
drm-fixes-2018-12-21:
final drm-fixes for 4.20
array_index_nospec patch, cc: stable
Very calm week, so either everything perfect or everyone on holidays
already. Same for -next btw, I merged a few things but nothing that should
block Dave's main merge window pull, so that one is still good to go.
Cheers, Daniel
The following changes since commit 7566ec393f4161572ba6f11ad5171fd5d59b0fbd:
Linux 4.20-rc7 (2018-12-16 15:46:55 -0800)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2018-12-21
for you to fetch changes up to b6aac625e579ca684448f8ace632f8dceb972afb:
Merge tag 'drm-misc-fixes-2018-12-20' of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes (2018-12-20 18:13:53 +0100)
----------------------------------------------------------------
final drm-fixes for 4.20
array_index_nospec patch, cc: stable
----------------------------------------------------------------
Daniel Vetter (1):
Merge tag 'drm-misc-fixes-2018-12-20' of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes
Gustavo A. R. Silva (1):
drm/ioctl: Fix Spectre v1 vulnerabilities
drivers/gpu/drm/drm_ioctl.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2018-12-21 13:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 13:39 Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-06 23:05 [PULL] drm-fixes Daniel Vetter
2023-01-06 23:05 ` Daniel Vetter
2023-01-06 23:58 ` pr-tracker-bot
2023-01-06 23:58 ` pr-tracker-bot
2022-09-30 22:19 Daniel Vetter
2022-09-30 22:19 ` Daniel Vetter
2022-09-30 23:29 ` pr-tracker-bot
2022-09-30 23:29 ` pr-tracker-bot
2021-10-01 16:57 Daniel Vetter
2021-10-01 17:45 ` pr-tracker-bot
2021-04-16 13:32 Daniel Vetter
2021-04-16 13:32 ` Daniel Vetter
2021-04-16 15:15 ` pr-tracker-bot
2021-04-16 15:15 ` pr-tracker-bot
2021-01-08 15:57 Daniel Vetter
2021-01-08 15:57 ` Daniel Vetter
2021-01-08 23:49 ` pr-tracker-bot
2021-01-08 23:49 ` pr-tracker-bot
2020-03-06 21:08 Daniel Vetter
2020-03-06 21:08 ` Daniel Vetter
2020-03-06 22:20 ` pr-tracker-bot
2020-03-06 22:20 ` pr-tracker-bot
2019-07-26 19:45 Daniel Vetter
2019-07-26 21:40 ` pr-tracker-bot
2019-01-11 23:06 Daniel Vetter
2019-01-11 23:06 ` Daniel Vetter
2019-01-12 18:45 ` pr-tracker-bot
2019-01-12 18:45 ` pr-tracker-bot
2012-11-23 16:58 [pull] drm-fixes Daniel Vetter
2012-11-25 19:57 ` Daniel Vetter
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=20181221133958.GA24222@phenom.ffwll.local \
--to=daniel.vetter@ffwll.ch \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maxime.ripard@bootlin.com \
--cc=rodrigo.vivi@intel.com \
--cc=torvalds@linux-foundation.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.