From: Christian Eggers <ceggers@arri.de>
To: Wolfram Sang <wsa@kernel.org>
Cc: "Oleksij Rempel" <linux@rempel-privat.de>,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"David Laight" <David.Laight@aculab.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"NXP Linux Team" <linux-imx@nxp.com>,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Krzysztof Kozlowski" <krzk@kernel.org>
Subject: Re: [PATCH v6 0/3] i2c: imx: Fix handling of arbitration loss
Date: Sun, 18 Oct 2020 12:44:10 +0200 [thread overview]
Message-ID: <1812241.n2eA9Fn7ml@n95hx1g2> (raw)
In-Reply-To: <20201010110658.GA4669@ninjato>
Hi Wolfram,
On Saturday, 10 October 2020, 13:06:58 CEST, Wolfram Sang wrote:
> > Changes in v5:
> Changes in v6 were missing... Because patch 1 was updated, I reverted it
> from for-current and will apply this series to for-next instead to give
> it some more time for testing.
can may patches be merged into for-current for -RC2 or RC3?
Best regards
Christian
next prev parent reply other threads:[~2020-10-18 10:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 11:03 [PATCH v6 0/3] i2c: imx: Fix handling of arbitration loss Christian Eggers
2020-10-09 11:03 ` [PATCH v6 1/3] i2c: imx: Fix reset of I2SR_IAL flag Christian Eggers
2020-10-10 11:09 ` Wolfram Sang
2020-12-01 7:34 ` Christian Eggers
2020-12-02 15:04 ` Wolfram Sang
2020-10-09 11:03 ` [PATCH v6 2/3] i2c: imx: Check for I2SR_IAL after every byte Christian Eggers
2020-10-10 11:09 ` Wolfram Sang
2020-10-09 11:03 ` [PATCH v6 3/3] i2c: imx: Don't generate STOP condition if arbitration has been lost Christian Eggers
2020-10-10 11:09 ` Wolfram Sang
2020-10-10 11:06 ` [PATCH v6 0/3] i2c: imx: Fix handling of arbitration loss Wolfram Sang
2020-10-18 10:44 ` Christian Eggers [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-09 11:02 Christian Eggers
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=1812241.n2eA9Fn7ml@n95hx1g2 \
--to=ceggers@arri.de \
--cc=David.Laight@aculab.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=o.rempel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).