From: Fengguang Wu
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Laurent Pinchart
Signed-off-by: Fengguang Wu
Signed-off-by: Julia Lawall
---
url:
https://github.com/0day-ci/linux/commits/Laurent-Pinchart/Cargo-cult-cleanup-in-atomic-drivers/20180120
From: Fengguang Wu
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Laurent Pinchart
Signed-off-by: Fengguang Wu
Signed-off-by: Julia Lawall
---
url:
https://github.com/0day-ci/linux/commits/Laurent-Pinchart/Cargo-cult-cleanup-in-atomic-drivers/20180120
moval")
Signed-off-by: Fengguang Wu
Signed-off-by: Julia Lawall
---
url:
https://github.com/0day-ci/linux/commits/Laurent-Pinchart/Cargo-cult-cleanup-in-atomic-drivers/20180120-183018
base: git://people.freedesktop.org/~airlied/linux.git drm-next
:: branch date: 3 hours ago
:: comm
Hi Maruthi,
FYI, the error/warning still remains.
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: f1182e58cded6542924c9ae92c1e9cf4da9c73d3
commit: 4ab7d004f9ff2e877caa267887360e1804b4edcf [1493/1583] ASoC: AMD: enable
ACP3x drivers build
config: cris-allyesconf
https://bugzilla.kernel.org/show_bug.cgi?id=198511
Christian König (christian.koe...@amd.com) changed:
What|Removed |Added
CC||christian.koe
https://bugzilla.kernel.org/show_bug.cgi?id=198511
--- Comment #13 from Barto (mister.free...@laposte.net) ---
the specs of my PC :
cpu : intel core 2 quad Q9650 ( 3 Ghz )
ram : 8 Gb DDR2
gpu : amd radeon HD4650 pcie
motherboard : gigabyte GA-P35-DS3L ( socket 775, chipset intel P35 )
window mana
From: Fengguang Wu
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Laurent Pinchart
Signed-off-by: Fengguang Wu
Signed-off-by: Julia Lawall
---
hdmi_connector.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/gpu/drm/msm/hdmi/hd
https://bugs.freedesktop.org/show_bug.cgi?id=103277
--- Comment #11 from dwagner ---
Just for you information: S3 resumes still do not work in 100% of attempts,
also with the current git version of
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
This is really frustrating.
https://bugs.freedesktop.org/show_bug.cgi?id=104602
--- Comment #2 from Jason Playne ---
Created attachment 136866
--> https://bugs.freedesktop.org/attachment.cgi?id=136866&action=edit
image showing the bad triangles
These triangles are not static, they flicker around the screen a fair bit
--
https://bugs.freedesktop.org/show_bug.cgi?id=104602
--- Comment #1 from Jason Playne ---
I am seeing the same with my vega64 on KDE Neon with the oibaf ppa.
packages are marked as 17.4~git1801200730.436ed6~oibaf~x
kernel: 4.15.0-041500rc5-generic
You can easily reproduce this by running the gr
/linux/commits/Laurent-Pinchart/Cargo-cult-cleanup-in-atomic-drivers/20180120-183018
base: git://people.freedesktop.org/~airlied/linux.git drm-next
config: i386-randconfig-x002-201802 (attached as .config)
compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
reproduce:
# save the attached .config
/commits/Laurent-Pinchart/Cargo-cult-cleanup-in-atomic-drivers/20180120-183018
base: git://people.freedesktop.org/~airlied/linux.git drm-next
config: i386-randconfig-n0-201802 (attached as .config)
compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
reproduce:
# save the attached .config to linux
Quoting Chris Wilson (2018-01-20 09:36:10)
> Quoting Matt Roper (2018-01-20 01:51:40)
> > GPU contexts are usually created with "normal" priority as a starting point
> > and
> > then may be adjusted from their either via explicit methods
> > (context_set_param)
> > or implicit methods (boosts/pen
Quoting Matt Roper (2018-01-20 01:51:40)
> GPU contexts are usually created with "normal" priority as a starting point
> and
> then may be adjusted from their either via explicit methods
> (context_set_param)
> or implicit methods (boosts/penalization due to runtime behavior). Let's
> allow
> a
14 matches
Mail list logo