From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org,
Chris Paterson <Chris.Paterson2@renesas.com>,
Biju Das <biju.das@bp.renesas.com>,
stable@vger.kernel.org,
Ben Hutchings <ben.hutchings@codethink.co.uk>
Subject: Re: [PATCH 0/6] Fix R-Car I2C data byte sent twice issue
Date: Sat, 2 Jun 2018 15:16:14 +0200 [thread overview]
Message-ID: <20180602131614.GD31493@kroah.com> (raw)
In-Reply-To: <1527600796-25901-1-git-send-email-fabrizio.castro@bp.renesas.com>
On Tue, May 29, 2018 at 02:33:10PM +0100, Fabrizio Castro wrote:
> Hello Greg,
>
> this series fixes an issue with the I2C driver of the Renesas R-Car and
> RZ/G1 family of chips. The issue is clearly visible with the CIP kernel
> (4.4) running on a iwg20d board from iWave due to the way the bq32000
> driver/device is interacting with the I2C driver/controller.
> In the stable kernel (4.4) there is no support for the iwg20d, I tried
> to replicate the same problem on a Koelsch board with no success, but
> the problem is there.
>
> Do you think this series is suitable for (4.4) stable considering I
> can't reproduce the problem on the Koelsch board?
It looks good, all now queued up.
greg k-h
prev parent reply other threads:[~2018-06-02 13:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 13:33 [PATCH 0/6] Fix R-Car I2C data byte sent twice issue Fabrizio Castro
2018-05-29 13:33 ` [PATCH 1/6] i2c: rcar: make sure clocks are on when doing clock calculation Fabrizio Castro
2018-05-29 13:33 ` [PATCH 2/6] i2c: rcar: rework hw init Fabrizio Castro
2018-05-29 13:33 ` [PATCH 3/6] i2c: rcar: remove unused IOERROR state Fabrizio Castro
2018-05-29 13:33 ` [PATCH 4/6] i2c: rcar: remove spinlock Fabrizio Castro
2018-05-29 13:33 ` [PATCH 5/6] i2c: rcar: refactor setup of a msg Fabrizio Castro
2018-05-29 13:33 ` [PATCH 6/6] i2c: rcar: init new messages in irq Fabrizio Castro
2018-05-29 17:19 ` [PATCH 0/6] Fix R-Car I2C data byte sent twice issue Wolfram Sang
2018-05-29 17:25 ` Wolfram Sang
2018-05-29 18:52 ` Fabrizio Castro
2018-05-29 19:16 ` Wolfram Sang
2018-05-29 18:08 ` Fabrizio Castro
2018-06-02 13:16 ` Greg Kroah-Hartman [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=20180602131614.GD31493@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Chris.Paterson2@renesas.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=biju.das@bp.renesas.com \
--cc=fabrizio.castro@bp.renesas.com \
--cc=linux-i2c@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.