From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 0518D37C0F3 for ; Tue, 30 Jun 2026 16:43:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782837835; cv=none; b=DogmoPP+kU9ogu+cyGcFB20snH9Grh/A+IRiBluOQVzMCtI6trQZECppqz0BH2VLD9ZM3LfBv8V9ezfIxox0Lz1Rn8HFDHRZgvm3FURSzFgHgyK/gN+1Cjp1IX1LTlKkICdH4Ou6is5gDOF0UwHuA3s+1YBBt+biPFcdwyxyvVQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782837835; c=relaxed/simple; bh=m4fT7HpFn8E51NABKyJEmwtwCezpdLYaRFz0wF4Gi+M=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=le0QSumEYeY0lzDHcGNUEjiKVTfq7KsYY5PgTvBetrMRQuDnT0o7Ci30SzRJfhtk6SsGznrlAFhN7EXdFKiEJ7O1vusr3zLdj2mkb6y52F1OXY6zCrCiV4FQHNT0f6CCzHoiHw2DajPgG9ie7lp+zZOgUQ2+4pxrW0wCidIqwaY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=gpnaG3oD; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="gpnaG3oD" Received: by smtp.kernel.org (Postfix) with ESMTPSA id EBE5C1F000E9; Tue, 30 Jun 2026 16:43:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1782837834; bh=m4fT7HpFn8E51NABKyJEmwtwCezpdLYaRFz0wF4Gi+M=; h=From:To:Cc:Subject:In-Reply-To:References:Date; b=gpnaG3oD++wj2K2BXJuk0zdKujoAuYwAyTrkq27hJu3ECF+O0+G+LnhSfd+DHnZwI HzWZqEprTh5IaAGA/CzZ1/esoREN+pTH5ggktWPSRZC2QF+aBgvvq892crOSUkpb5K cP4gOwmp4ipP4HB/p80rDpR5Q1k74ZLq1aQvYKk1bGRTDCr9H8wVpClKUW19asgH2A F6NgwUQAWPWkR4Iik2y6FP1MjeLvvtG7lQgKoN0SI63r0KNWhubjFgTVCGlcg4F0fa 7rKrXZC2JWAdso8BaNB9vMjuEgM4HbH+RB1ZEJiK3I9+WPnpBSbxHV7bPp9V4dj0K4 uFBQrNsoc4e4Q== From: Thomas Gleixner To: Kemeng Shi , maz@kernel.org Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, shikemeng@huaweicloud.com Subject: Re: [PATCH v3 4/6] irqchip/gic-v3-its: Add ITS address info in more error logs In-Reply-To: <20260623020135.3584-5-shikemeng@huaweicloud.com> References: <20260623020135.3584-1-shikemeng@huaweicloud.com> <20260623020135.3584-5-shikemeng@huaweicloud.com> Date: Tue, 30 Jun 2026 18:43:51 +0200 Message-ID: <87zf0cou60.ffs@fw13> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Tue, Jun 23 2026 at 10:01, Kemeng Shi wrote: > We have a lot of logs containing ITS address info which is helpful to We have nothing ... > distiguish which ITS occurs error. Just add ITS address info into more > exsiting error logs. existing 'Just add ITS ...' does tell WHAT the patch does but does not explian WHY this is required, useful or whatever reason you have.