[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <j2l7tu24itjelylrgwe6gdsy3mfrw3dnve4rdofmri3z7xdroc@se56t5ylmdak>
Date: Tue, 26 Mar 2024 01:36:41 +0100
From: Andi Shyti <andi.shyti@...nel.org>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc: linux-i2c@...r.kernel.org, asahi@...ts.linux.dev,
chrome-platform@...ts.linux.dev, imx@...ts.linux.dev, linux-actions@...ts.infradead.org,
linux-amlogic@...ts.infradead.org, linux-arm-kernel@...ts.infradead.org,
linux-arm-msm@...r.kernel.org, linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
linux-mediatek@...ts.infradead.org, linux-mips@...r.kernel.org, linux-omap@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, linux-renesas-soc@...r.kernel.org,
linux-riscv@...ts.infradead.org, linux-rockchip@...ts.infradead.org,
linux-rpi-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com, linux-sunxi@...ts.linux.dev, linux-tegra@...r.kernel.org,
openbmc@...ts.ozlabs.org, virtualization@...ts.linux.dev
Subject: Re: [PATCH 00/64] i2c: reword i2c_algorithm according to newest
specification
Hi Wolfram,
> > @Andi: are you okay with this approach? It means you'd need to merge
> > -rc2 into your for-next branch. Or rebase if all fails.
>
> I think it's a good plan, I'll try to support you with it.
Do you feel more comfortable if I take the patches as soon as
they are reviewd?
So far I have tagged patch 1-4 and I can already merge 2,3,4 as
long as you merge patch 1.
Andi
Powered by blists - more mailing lists