From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (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 E18091A3144; Fri, 4 Apr 2025 09:20:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.176.79.56 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743758457; cv=none; b=t5/koQe2f5OwIqfOp79EiV7xJ4q5ywaeCodViEbcCtxsyIM90/qCzL8x9nfT8/bV4gGXozMUqcpx48tiUX56Xo63Wnsf0H4ExW4cmsyECld7Fn9wsn2mWrpiLSx6q9QVIN6e5G4S/UmFD727vKnoMV3q0esJeLJ5K+cPFTBRtdQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743758457; c=relaxed/simple; bh=/qhPQqDfPIlOx7DCzaQ3g+N4TaadMGauJvk2V7rJTEg=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=Wnnr+uGgEsouy/pBms0d/2MOuao5QP1h9uOsGg9q/K39oei8lIM3KsB3BJix8JESpYS9nIe7WRh5ZsQIUK9/m83we18H++2T2kpUlEm01fSfFgFiGEOeUQhUCxG8ZhxfFwKF+je71PWwK1t+q9KQbF8A/InIwMaO2BOhRMK3OJk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com; spf=pass smtp.mailfrom=huawei.com; arc=none smtp.client-ip=185.176.79.56 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=huawei.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=huawei.com Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4ZTY3Y5c5Kz67QRQ; Fri, 4 Apr 2025 17:20:09 +0800 (CST) Received: from frapeml500008.china.huawei.com (unknown [7.182.85.71]) by mail.maildlp.com (Postfix) with ESMTPS id A7F9E14080B; Fri, 4 Apr 2025 17:20:51 +0800 (CST) Received: from localhost (10.203.177.66) by frapeml500008.china.huawei.com (7.182.85.71) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Fri, 4 Apr 2025 11:20:50 +0200 Date: Fri, 4 Apr 2025 10:20:49 +0100 From: Jonathan Cameron To: Zaid Alali CC: , , , , , , , , , , , , , , , , Subject: Re: [PATCH v5 3/9] ACPI: APEI: EINJ: Fix kernel test robot sparse warning Message-ID: <20250404102049.0000308c@huawei.com> In-Reply-To: <20250403231339.23708-4-zaidal@os.amperecomputing.com> References: <20250403231339.23708-1-zaidal@os.amperecomputing.com> <20250403231339.23708-4-zaidal@os.amperecomputing.com> X-Mailer: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: linux-acpi@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-ClientProxiedBy: lhrpeml500011.china.huawei.com (7.191.174.215) To frapeml500008.china.huawei.com (7.182.85.71) On Thu, 3 Apr 2025 16:13:33 -0700 Zaid Alali wrote: Probably don't need to mention robot in the commit title. > This patch fixes the kernel test robot warning reported here: > https://lore.kernel.org/all/202410241620.oApALow5-lkp@intel.com/ Good perhaps to use the tags suggested in that message. That helps acknowledge the usefulness of that service and them tracking the closure of reports. > > Signed-off-by: Zaid Alali Otherwise you fixed the one thing I pointed out in v4 so Reviewed-by: Jonathan Cameron