From: Wolfram Sang <wsa@the-dreams.de>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-i2c@vger.kernel.org,
Sergey Larin <cerg2010cerg2010@mail.ru>
Subject: Re: [PATCH 1/2] Revert "i2c: algo-bit: init the bus to a known state"
Date: Tue, 26 Jun 2018 11:37:09 +0900 [thread overview]
Message-ID: <20180626023709.jfr7vee7tumarz3h@ninjato> (raw)
In-Reply-To: <20180616133757.5994-2-wsa+renesas@sang-engineering.com>
On Sat, Jun 16, 2018 at 10:37:56PM +0900, Wolfram Sang wrote:
> This reverts commit 3e5f06bed72fe72166a6778f630241a893f67799. As per
> bugzilla #200045, this caused a regression. I don't really see a way to
> fix it without having the hardware. So, revert the patch and I will fix
> the issue I was seeing originally in the i2c-gpio driver itself. I
> couldn't find new users of this algorithm since, so there should be no
> one depending on the new behaviour.
>
> Reported-by: Sergey Larin <cerg2010cerg2010@mail.ru>
> Fixes: 3e5f06bed72f ("i2c: algo-bit: init the bus to a known state")
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Applied to for-current, thanks!
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-06-26 2:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 13:37 [PATCH 0/2] i2c: algos: bit: revert to fix regression (#200045) Wolfram Sang
2018-06-16 13:37 ` [PATCH 1/2] Revert "i2c: algo-bit: init the bus to a known state" Wolfram Sang
2018-06-26 2:37 ` Wolfram Sang [this message]
2018-06-16 13:37 ` [PATCH 2/2] i2c: algos: bit: mention our experience about initial states Wolfram Sang
2018-06-18 16:03 ` Alex Deucher
2018-06-26 2:37 ` Wolfram Sang
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=20180626023709.jfr7vee7tumarz3h@ninjato \
--to=wsa@the-dreams.de \
--cc=cerg2010cerg2010@mail.ru \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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