[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240909-jugular-cucumber-b7d9bc614f74@wendy>
Date: Mon, 9 Sep 2024 12:22:22 +0100
From: Conor Dooley <conor.dooley@...rochip.com>
To: Andi Shyti <andi.shyti@...nel.org>
CC: Heikki Krogerus <heikki.krogerus@...ux.intel.com>, Jarkko Nikula
<jarkko.nikula@...ux.intel.com>, Andy Shevchenko
<andriy.shevchenko@...ux.intel.com>, Mika Westerberg
<mika.westerberg@...ux.intel.com>, Jan Dabros <jsd@...ihalf.com>,
<linux-i2c@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 7/7] i2c: designware: Group all DesignWare drivers
under a single option
On Thu, Sep 05, 2024 at 10:46:02PM +0200, Andi Shyti wrote:
> Hi Heikki,
>
> On Tue, Sep 03, 2024 at 05:25:06PM GMT, Heikki Krogerus wrote:
> > There are quite a few drivers and options for the DesignWare
> > I2C adapter in the Kconfig. Grouping all of them under the
> > I2C_DESIGNWARE_CORE. That makes the menuconfig a bit more
> > easier to understand.
> >
> > Signed-off-by: Heikki Krogerus <heikki.krogerus@...ux.intel.com>
>
> Thanks for your patch, I can take this only after the other
> patches have been taken in.
I assume then that you're expecting the prereqs to go through the
various arch trees? Is this not trivial enough that you could chuck it
on a dedicated branch in your tree and if, for some reason, there's a
non-trivial conflict the affected could pull it in?
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists