Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Petre Rodan <petre.rodan@subdimension.ro>
Cc: "Jonathan Cameron" <jonathan.cameron@huawei.com>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH] iio: accel: bma220: move set_wdt() out of bma220_core
Date: Mon, 27 Oct 2025 14:11:42 +0000	[thread overview]
Message-ID: <20251027141142.555a05e7@jic23-huawei> (raw)
In-Reply-To: <aP8Cx7gMxGfpfb6n@sunspire.home.arpa>

On Mon, 27 Oct 2025 07:27:35 +0200
Petre Rodan <petre.rodan@subdimension.ro> wrote:

> Hello Jonathan.
> 
> On Thu, Oct 23, 2025 at 06:23:18PM +0100, Jonathan Cameron wrote:
> > On Wed, 22 Oct 2025 14:50:18 +0300
> > Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> >   
> > > On Tue, Oct 21, 2025 at 01:31:49PM +0300, Petre Rodan wrote:  
> > > > Move bma220_set_wdt() into bma220_i2c.c instead of using a conditional
> > > > based on i2c_verify_client() in bma220_core.c that would make core
> > > > always depend on the i2c module.    
> > > 
> > > Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > 
> > > But Kconfig for this driver is a bit strange. Usually we do other way around,
> > > i.e. make user visible selection of the glue drivers, while core is selected if
> > > at least one of the leaf driver selected by the user.
> > >   
> > This comes up from time to time.  There kind of isn't a right answer
> > to my mind in the trade off between complexity of configuration 
> > and desire for minimum useful set of Kconfig symbols and people wanting
> > to build only exactly what they want.  So we've ended up with a mix.
> > 
> > I don't mind setting a policy on this for new code going forwards, but
> > that means we need to decide which approach we prefer and document
> > it somewhere.  
> 
> I will come back with a new patch to Kconfig once you decide what is the best way to handle dependecies, but in the meantime can you please accept this current patch?
> 
> I keep getting automated errors that would be fixed by it:
> 
> https://lore.kernel.org/oe-kbuild-all/202510210604.mAtgE54g-lkp@intel.com/
> https://lore.kernel.org/oe-kbuild-all/202510222324.SxYlIaLW-lkp@intel.com/
> https://lore.kernel.org/oe-kbuild-all/202510271347.115BMnsC-lkp@intel.com/

Done. Was travelling (and on wrong computer).

Should be resolved now.
> 
> If the current patch does not correctly reference the automated 0day-ci reports please tell me what I should change within my b4 workflow.
> 
> thank you,
> peter


  reply	other threads:[~2025-10-27 14:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21 10:31 [PATCH] iio: accel: bma220: move set_wdt() out of bma220_core Petre Rodan
2025-10-22 11:50 ` Andy Shevchenko
2025-10-23 17:23   ` Jonathan Cameron
2025-10-23 18:37     ` Andy Shevchenko
2025-10-27  5:27     ` Petre Rodan
2025-10-27 14:11       ` Jonathan Cameron [this message]
2025-10-27 14:10 ` 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=20251027141142.555a05e7@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=nuno.sa@analog.com \
    --cc=petre.rodan@subdimension.ro \
    /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