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 E51D82820C6 for ; Thu, 15 Jan 2026 17:12:25 +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=1768497149; cv=none; b=BhVrx3AiCpXEsynOiP3Eydw8yIuUJys1igOTDqH2b7dLrShpIDjSnCnlvepqKXAqgH0BSm2pELbr9PB84hWZYUsC5MQEaN+ycysu2SUls2YG8zaJcGE5zrAYFhmsAwoe7M5xz4MDbVKgUHENUnVHDm29weHXSEHG2h0g3iI+KTQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768497149; c=relaxed/simple; bh=x/eIzLLXpaI8DSRHWDzRJDR2wBDAqIy+IK0ssQnmEr8=; h=Date:From:To:CC:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=hmRbtN3p7vFstVeGOE8VFA+XUD0gd8bS7F0WKi2CyBJ2vwyean1Fhlp0vjiYwyIQu63zaAi0fu+57JkV1ZtWZ4fmqeRqf3bh6G8iZ+OECLEoFsBBYGCSEy9/HkFfcd7AyZBg/dCSDsy7jYknz0K04Biss32KzHFIdhWEi489/00= 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.224.150]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4dsV063fr2zJ46Dv; Fri, 16 Jan 2026 01:12:06 +0800 (CST) Received: from dubpeml100005.china.huawei.com (unknown [7.214.146.113]) by mail.maildlp.com (Postfix) with ESMTPS id 1A7F440539; Fri, 16 Jan 2026 01:12:23 +0800 (CST) Received: from localhost (10.203.177.15) by dubpeml100005.china.huawei.com (7.214.146.113) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.36; Thu, 15 Jan 2026 17:12:22 +0000 Date: Thu, 15 Jan 2026 17:12:20 +0000 From: Jonathan Cameron To: Alexandre Belloni CC: Frank Li , , , , , , , Subject: Re: [PATCH 1/1] i3c: Add stub functions when I3C support is disabled Message-ID: <20260115171220.000001b7@huawei.com> In-Reply-To: <176840281753.1259180.16475027635174872850.b4-ty@bootlin.com> References: <20251230145718.4088694-1-Frank.Li@nxp.com> <176840281753.1259180.16475027635174872850.b4-ty@bootlin.com> X-Mailer: Claws Mail 4.3.0 (GTK 3.24.42; x86_64-w64-mingw32) Precedence: bulk X-Mailing-List: linux-iio@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: lhrpeml500009.china.huawei.com (7.191.174.84) To dubpeml100005.china.huawei.com (7.214.146.113) On Wed, 14 Jan 2026 16:02:06 +0100 Alexandre Belloni wrote: > On Tue, 30 Dec 2025 09:57:18 -0500, Frank Li wrote: > > When I3C is disabled, unused functions are removed by the linker because > > the driver relies on regmap and no I3C devices are registered, so normal > > I3C paths are never called. > > > > However, some drivers may still call low-level I3C transfer helpers. > > Provide stub implementations to avoid adding conditional ifdefs everywhere. > > > > [...] > > Applied, thanks! > > [1/1] i3c: Add stub functions when I3C support is disabled > https://git.kernel.org/i3c/c/8564f88df202 > > Best regards, > Hi Alexandre, This is going to make for an 'interesting' merge window as I'm getting build failures without that patch. I don't suppose you'd mind doing an immutable branch? If not, maybe best bet is some local ifdefs that we back out next merge window. I don't really want to kick the driver back a cycle just for this. Thanks, Jonathan