public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Frank Li <Frank.Li@nxp.com>, <andriy.shevchenko@intel.com>,
	<carlos.song@nxp.com>, <fluturel.adrian@gmail.com>,
	<linux-i3c@lists.infradead.org>, <linux-iio@vger.kernel.org>,
	<lkp@intel.com>, <oe-kbuild-all@lists.linux.dev>
Subject: Re: [PATCH 1/1] i3c: Add stub functions when I3C support is disabled
Date: Thu, 15 Jan 2026 17:12:20 +0000	[thread overview]
Message-ID: <20260115171220.000001b7@huawei.com> (raw)
In-Reply-To: <176840281753.1259180.16475027635174872850.b4-ty@bootlin.com>

On Wed, 14 Jan 2026 16:02:06 +0100
Alexandre Belloni <alexandre.belloni@bootlin.com> 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



  reply	other threads:[~2026-01-15 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30 14:57 [PATCH 1/1] i3c: Add stub functions when I3C support is disabled Frank Li
2026-01-14 15:02 ` Alexandre Belloni
2026-01-15 17:12   ` Jonathan Cameron [this message]
2026-01-20 23:02     ` Alexandre Belloni
2026-01-21 20:00       ` Jonathan Cameron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260115171220.000001b7@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=Frank.Li@nxp.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=carlos.song@nxp.com \
    --cc=fluturel.adrian@gmail.com \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox