public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@kernel.org>
To: Gabor Juhos <j4g8y7@gmail.com>
Cc: Wolfram Sang <wsa@kernel.org>,
	 Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	 Russell King <rmk+kernel@armlinux.org.uk>,
	Andrew Lunn <andrew@lunn.ch>, Hanna Hawa <hhhawa@amazon.com>,
	 Robert Marko <robert.marko@sartura.hr>,
	linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	 linux-kernel@vger.kernel.org, Linus Walleij <linusw@kernel.org>,
	stable@vger.kernel.org,  Imre Kaloz <kaloz@openwrt.org>
Subject: Re: [PATCH v4 0/2] i2c: pxa: fix I2C communication on Armada 3700
Date: Fri, 20 Mar 2026 00:03:00 +0100	[thread overview]
Message-ID: <abyAI0ANDdxYO3uD@zenone.zhora.eu> (raw)
In-Reply-To: <20260226-i2c-pxa-fix-i2c-communication-v4-0-797a091dae87@gmail.com>

Hi Gabor,

> Gabor Juhos (2):
>       i2c: pxa: defer reset on Armada 3700 when recovery is used

I merged this in i2c/i2c-host-fixes.

>       i2c: pxa: handle 'Early Bus Busy' condition on Armada 3700

This one can't really be considered as a fix and I removed the
"Cc: stable" tag from the commit log.

As of now I merged it in my i2c/i2c-host-next, which is my
testing branch. Once the fix will be taken, I will move it to the
i2c/i2c-host for the next merge window.

Thanks,
Andi

      parent reply	other threads:[~2026-03-19 23:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 13:11 [PATCH v4 0/2] i2c: pxa: fix I2C communication on Armada 3700 Gabor Juhos
2026-02-26 13:11 ` [PATCH v4 1/2] i2c: pxa: defer reset on Armada 3700 when recovery is used Gabor Juhos
2026-02-26 13:11 ` [PATCH v4 2/2] i2c: pxa: handle 'Early Bus Busy' condition on Armada 3700 Gabor Juhos
2026-02-27  0:13 ` [PATCH v4 0/2] i2c: pxa: fix I2C communication " Linus Walleij
2026-03-19 23:03 ` Andi Shyti [this message]

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=abyAI0ANDdxYO3uD@zenone.zhora.eu \
    --to=andi.shyti@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hhhawa@amazon.com \
    --cc=j4g8y7@gmail.com \
    --cc=kaloz@openwrt.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=robert.marko@sartura.hr \
    --cc=stable@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=wsa@kernel.org \
    /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