On 12/28/22 9:51 PM, Patchwork wrote:
== Series Details ==
Series: Fixes integer overflow or integer truncation issues in page lookups,
ttm place configuration and scatterlist creation
URL : https://patchwork.freedesktop.org/series/112279/
State : warning
== Summary ==
Error: dim checkpa
On Thu, Dec 22, 2022, at 12:46, Andrzej Hajda wrote:
> __xchg will be used for non-atomic xchg macro.
>
> Signed-off-by: Andrzej Hajda
> ---
> arch/arc/include/asm/cmpxchg.h | 4 ++--
Reviewed-by: Arnd Bergmann
for all the arch/*/include/asm/cmpxchg.h changes.
Since these patches are all the s
Forgive me late response - Holidays,
On 22.12.2022 18:21, Andrew Morton wrote:
On Thu, 22 Dec 2022 12:46:16 +0100 Andrzej Hajda
wrote:
Hi all,
I hope there will be place for such tiny helper in kernel.
Quick cocci analyze shows there is probably few thousands places
where it could be useful
On 22.12.2022 07:34, Ankit Nautiyal wrote:
The dsb context should be already checked for NULL, before dsb_commit gets
called. So remove the check for dsb inside dsb_commit.
Signed-off-by: Ankit Nautiyal
---
drivers/gpu/drm/i915/display/intel_dsb.c | 2 +-
1 file changed, 1 insertion(+), 1 de
__xchg will be used for non-atomic xchg macro.
Signed-off-by: Andrzej Hajda
Reviewed-by: Arnd Bergmann
---
arch/alpha/include/asm/cmpxchg.h | 6 +++---
arch/arc/include/asm/cmpxchg.h | 4 ++--
arch/arm/include/asm/cmpxchg.h | 4 ++--
arch/arm64/include/asm/cmpxchg.h | 4 ++--
== Series Details ==
Series: Introduce __xchg, non-atomic xchg (rev2)
URL : https://patchwork.freedesktop.org/series/112169/
State : warning
== Summary ==
Error: dim checkpatch failed
8d448159f384 arch/alpha: rename internal name __xchg to __arch_xchg
fbe161e26670 arch: rename all internal nam
== Series Details ==
Series: Introduce __xchg, non-atomic xchg (rev2)
URL : https://patchwork.freedesktop.org/series/112169/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12528 -> Patchwork_112169v2
Summary
---
**FAI
There are new cases where we want to block i915 probe, such
as when experimenting or developing the new Xe driver.
But also, with the new hibrid cards, users or developers might
want to use i915 only on integrated and fully block the probe
of the i915 for the discrete. Or vice versa.
Oh, and ther
On Thu, 22 Dec 2022 03:46:29 PST (-0800), andrzej.ha...@intel.com wrote:
__xchg will be used for non-atomic xchg macro.
Signed-off-by: Andrzej Hajda
---
arch/riscv/include/asm/atomic.h | 2 +-
arch/riscv/include/asm/cmpxchg.h | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --
== Series Details ==
Series: drm/i915: Expand force_probe to block probe of devices as well.
URL : https://patchwork.freedesktop.org/series/112292/
State : warning
== Summary ==
Error: dim checkpatch failed
2802730b7726 drm/i915: Expand force_probe to block probe of devices as well.
-:100: WAR
If intel_gvt_dma_map_guest_page failed, it will call
ppgtt_invalidate_spt, which will finally free the spt.
But the caller function ppgtt_populate_spt_by_guest_entry
does not notice that, it will free spt again in its error
path.
Fix this by canceling the mapping of DMA address and freeing sub
== Series Details ==
Series: drm/i915/gvt: fix double-free bug in split_2MB_gtt_entry (rev9)
URL : https://patchwork.freedesktop.org/series/108732/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12528 -> Patchwork_108732v9
S
On Thu, Dec 29, 2022 at 11:12:30AM -0500, Rodrigo Vivi wrote:
> There are new cases where we want to block i915 probe, such
> as when experimenting or developing the new Xe driver.
>
> But also, with the new hibrid cards, users or developers might
> want to use i915 only on integrated and fully bl
This patch series changes DMC loading to be backwards-compatible by
removing version checking and preparing the driver to load from blobs
unversioned filenames.
Next DMC releases should start using using unversioned filenames and the
code should be changed to use them when that happens. It's likel
New DMC releases in linux-firmware will stop using version number in
blob filenames. This new convention provides the following benefits:
1. It simplifies code maintenance, as new DMC releases for a platform
using the new convention will always use the same filename for the
blob.
2.
Currently there is no DMC version requirement with respect to how i915
interacts with it and new versions of the firmware serve as drop-in
replacements of older ones. As such, do not require specific versions.
References: https://lore.kernel.org/r/y3081s7c5ksut...@intel.com
Signed-off-by: Gustavo
== Series Details ==
Series: drm/i915/dmc: Make firmware loading backwards-compatible (rev3)
URL : https://patchwork.freedesktop.org/series/112116/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: drm/i915/dmc: Make firmware loading backwards-compatible (rev3)
URL : https://patchwork.freedesktop.org/series/112116/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12528 -> Patchwork_112116v3
S
18 matches
Mail list logo
