Re: [Intel-gfx] (no subject)

2023-06-20 Thread philly j
  
  

 Listen, here’s the problem I’m having guys and I need someone to reply back to 
me. Because I wrote to FSF and they wrote me right back and I join their and I 
have no problem with free software and complain but I don’t exactly know what 
you want me to do and I don’t have “git”   on my windows computer. And it seems 
like you guys are making it hard for me to do anything in the first place I 
can’t even connect to the Internet can someone help me out?
  
  
what problem am Iresolving  

  
  
  
  

  
  
>   
> On Jun 20, 2023 at 7:55 PM,   (mailto:patchw...@emeril.freedesktop.org)>  wrote:
>   
>   
>   
>  == Series Details == Series: drm/i915:fix kernel-doc trivial warnings URL : 
> https://patchwork.freedesktop.org/series/119620/ State : failure == Summary 
> == Error: patch 
> https://patchwork.freedesktop.org/api/1.0/series/119620/revisions/1/mbox/ not 
> applied Applying: drm/i915:fix kernel-doc trivial warnings Using index info 
> to reconstruct a base tree... M drivers/gpu/drm/i915/i915_active.h M 
> drivers/gpu/drm/i915/i915_gpu_error.c M drivers/gpu/drm/i915/i915_perf.c M 
> drivers/gpu/drm/i915/i915_scatterlist.h M drivers/gpu/drm/i915/i915_utils.h M 
> drivers/gpu/drm/i915/i915_vma_resource.h Falling back to patching base and 
> 3-way merge... Auto-merging drivers/gpu/drm/i915/i915_vma_resource.h 
> Auto-merging drivers/gpu/drm/i915/i915_utils.h Auto-merging 
> drivers/gpu/drm/i915/i915_scatterlist.h Auto-merging 
> drivers/gpu/drm/i915/i915_perf.c CONFLICT (content): Merge conflict in 
> drivers/gpu/drm/i915/i915_perf.c Auto-merging 
> drivers/gpu/drm/i915/i915_gpu_error.c CONFLICT (content): Merge conflict in 
> drivers/gpu/drm/i915/i915_gpu_error.c error: Failed to merge in the changes. 
> hint: Use 'git am --show-current-patch=diff' to see the failed patch Patch 
> failed at 0001 drm/i915:fix kernel-doc trivial warnings When you have 
> resolved this problem, run "git am --continue". If you prefer to skip this 
> patch, run "git am --skip" instead. To restore the original branch and stop 
> patching, run "git am --abort". Build failed, no error log produced  
>
>   
  
  


Re: [Intel-gfx] ✗ Fi.CI.BUILD: git am --abort

2023-06-18 Thread philly j
 
 

 
 
 
 
>  
>  
>  
> "git am --abort"  
>
>  
>
>  
>
>  
> On Jun 16, 2023 at 10:03 AM,   (mailto:patchw...@emeril.freedesktop.org)>  wrote:
>  
>  
>  
>  == Series Details == Series: Add vfio_device cdev for iommufd support 
> (rev17) URL : https://patchwork.freedesktop.org/series/113696/ State : 
> failure == Summary == Error: patch 
> https://patchwork.freedesktop.org/api/1.0/series/113696/revisions/17/mbox/ 
> not applied Applying: vfio: Allocate per device file structure Applying: 
> vfio: Refine vfio file kAPIs for KVM Applying: vfio: Accept vfio device file 
> in the KVM facing kAPI Applying: kvm/vfio: Prepare for accepting vfio device 
> fd Applying: kvm/vfio: Accept vfio device file from userspace Applying: vfio: 
> Pass struct vfio_device_file * to vfio_device_open/close() Applying: vfio: 
> Block device access via device fd until device is opened Applying: vfio: Add 
> cdev_device_open_cnt to vfio_group Applying: vfio: Make vfio_df_open() single 
> open for device cdev path Applying: vfio-iommufd: Move noiommu compat 
> validation out of vfio_iommufd_bind() Applying: vfio-iommufd: Split 
> bind/attach into two steps Applying: vfio: Record devid in vfio_device_
file Applying: vfio-iommufd: Add detach_ioas support for physical VFIO devices 
Applying: iommufd/device: Add iommufd_access_detach() API Applying: 
vfio-iommufd: Add detach_ioas support for emulated VFIO devices error: sha1 
information is lacking or useless (drivers/vfio/iommufd.c). error: could not 
build fake ancestor hint: Use 'git am --show-current-patch=diff' to see the 
failed patch Patch failed at 0015 vfio-iommufd: Add detach_ioas support for 
emulated VFIO devices When you have resolved this problem, run "git am 
--continue". If you prefer to skip this patch, run "git am --skip" instead. To 
restore the original branch and stop patching, run "git am --abort". Build 
failed, no error log produced 
>
>  
 
 
 

Re: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Use non traceable api in display trace code

2023-06-13 Thread philly j
  
  

 How do I do that? I just need to fix all this
  
Like, how does the system make changes on it when it’s not even plugged in I 
factory reset it unplug it once you’re done next day it’s like all different 
settings of   configuration files everything
  
  
  
  
  
  

  
  
>   
> On Jun 13, 2023 at 9:02 PM,   (mailto:patchw...@emeril.freedesktop.org)>  wrote:
>   
>   
>   
>  == Series Details == Series: Use non traceable api in display trace code URL 
> : https://patchwork.freedesktop.org/series/119303/ State : warning == Summary 
> == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each 
> commit won't be checked separately.  
>
>   
  
  


Re: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Use non traceable api in display trace code

2023-06-13 Thread philly j
  
  

 Why is this going on what do I need to do to secure everything I’m tired of 
all my devices not working I didn’t ask for this I’ve learned a lot but I’m so 
frustrated   
  
  
  
  
  
  
  

  
  
>   
> On Jun 13, 2023 at 9:02 PM,   (mailto:patchw...@emeril.freedesktop.org)>  wrote:
>   
>   
>   
>  == Series Details == Series: Use non traceable api in display trace code URL 
> : https://patchwork.freedesktop.org/series/119303/ State : warning == Summary 
> == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each 
> commit won't be checked separately.  
>
>