From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1B5B82139C9 for ; Sat, 28 Feb 2026 16:04:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772294657; cv=none; b=iPoynnT3Rd9J2JsXQT5i2oZg61bKWQmQS+nPfKUv0lIrceQ1Qdw2tbR4YPwYLwiWipIxWL+wb2VHPC23RXfO0GhfPKQzOPktKS507Ce4SYAHQ802H6AGTnMFZAFviQJrXTQcllCCHOnFiJ5QCmbq80GTvbUkQTV0UK5lfDF99FI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772294657; c=relaxed/simple; bh=VqoqwReNyK4D8hI7bVL5FnWWjw9JOwqFRBdBg0EIDo0=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=tDSmPYT//fjglufywbK1T/kS07/C0xG1CVn4GYdSrORdAwPO9ExzbE6leoKRGdEEpW2AXfrx6jSvrGbI3tdQcD2NuSvcqKMRvymo3j+nek+ImgEuiDgO/WHmFtMoeo11xL47mO8jEDSQCh7d92MKzAzf/dJ8QQyfZoQogCeSkCE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=MyibQhlj; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="MyibQhlj" Received: by smtp.kernel.org (Postfix) with ESMTPSA id CC098C116D0; Sat, 28 Feb 2026 16:04:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772294656; bh=VqoqwReNyK4D8hI7bVL5FnWWjw9JOwqFRBdBg0EIDo0=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=MyibQhljkF/0xj9qWOrOF8chMi/2NvrW1/QeXjahOp4xSseT3FkDVMncM5FOlDrGP ca/1hhlBRjytXhuYklzhUAmdF78wKg92TPnU+gAJxAMwD8C2/avdWz/y1gWfBkTZYA jIkknUSYpMy+z50Q2dEeEd3MVfHVJ7i/VyVeMhrHr4SOxrhMxni8aijh9RjMKciLFs yGFPdVD11bS3ZL8f0kfrnn3eUbNna1k00+H7YY4VleOjV806n/kY1jz2HEouKKMimu +cTDsIp4Zt7K4SLSIHY8VJiA72CMR165V1ZzTf1uVKsh7AQhyIWBFx3+/9T94KQ2l2 VRNJKAw+T6DZQ== Date: Sat, 28 Feb 2026 08:04:14 -0800 From: Jakub Kicinski To: Riana Tauro Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org, aravind.iddamsetty@linux.intel.com, anshuman.gupta@intel.com, rodrigo.vivi@intel.com, joonas.lahtinen@linux.intel.com, simona.vetter@ffwll.ch, airlied@gmail.com, pratik.bari@intel.com, joshua.santosh.ranjan@intel.com, ashwin.kumar.kulkarni@intel.com, shubham.kumar@intel.com, ravi.kishore.koppuravuri@intel.com, raag.jadav@intel.com, anvesh.bakwad@intel.com, Zack McKevitt , Lijo Lazar , Hawking Zhang , "David S. Miller" , Paolo Abeni , Eric Dumazet , netdev@vger.kernel.org Subject: Re: [PATCH v9 1/5] drm/ras: Introduce the DRM RAS infrastructure over generic netlink Message-ID: <20260228080414.6f1256cc@kernel.org> In-Reply-To: <20260228080858.3063532-8-riana.tauro@intel.com> References: <20260228080858.3063532-7-riana.tauro@intel.com> <20260228080858.3063532-8-riana.tauro@intel.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sat, 28 Feb 2026 13:38:25 +0530 Riana Tauro wrote: > Documentation/gpu/drm-ras.rst | 103 +++++++ > Documentation/gpu/index.rst | 1 + > Documentation/netlink/specs/drm_ras.yaml | 115 ++++++++ > drivers/gpu/drm/Kconfig | 10 + > drivers/gpu/drm/Makefile | 1 + > drivers/gpu/drm/drm_drv.c | 6 + > drivers/gpu/drm/drm_ras.c | 354 +++++++++++++++++++++++ > drivers/gpu/drm/drm_ras_genl_family.c | 42 +++ > drivers/gpu/drm/drm_ras_nl.c | 56 ++++ > drivers/gpu/drm/drm_ras_nl.h | 24 ++ > include/drm/drm_ras.h | 75 +++++ > include/drm/drm_ras_genl_family.h | 17 ++ > include/uapi/drm/drm_ras.h | 49 ++++ Doesn't apply to my local trees any more but _looks_ right :) Assuming ./tools/net/ynl/ynl-regen.sh -f doesn't result in a dirty tree: Acked-by: Jakub Kicinski > + if (!info->attrs || > + !info->attrs[DRM_RAS_A_ERROR_COUNTER_ATTRS_NODE_ID] || > + !info->attrs[DRM_RAS_A_ERROR_COUNTER_ATTRS_ERROR_ID]) > + return -EINVAL; Sorry for not noticing earlier but you could use GENL_REQ_ATTR_CHECK() here. It will give the user a nice error pointing out which attr was missing (assuming user space uses a competent ynl-based library).