linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: "Radosław Pietrzyk" <radoslaw.pietrzyk@gmail.com>
Cc: Pierre Yves MORDRET <pierre-yves.mordret@st.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@st.com>,
	"open list:I2C SUBSYSTEM" <linux-i2c@vger.kernel.org>,
	"moderated list:ARM/STM32 ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i2c: stm32: Fixes multibyte transfer for STM32F4 I2C controller
Date: Thu, 7 Dec 2017 11:52:29 +0100	[thread overview]
Message-ID: <20171207105229.jxxyfofsgub27nip@ninjato> (raw)
In-Reply-To: <CAFvLkMTsgxpjoGRgq7J0NFkT=YsOTYL6smkVhOPcfD=26Hzutg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 312 bytes --]

On Tue, Oct 24, 2017 at 01:45:43PM +0200, Radosław Pietrzyk wrote:
> I'm afraid that didn't help and the problem still exists even with
> those patches applied.

So, my reading is: There is an issue which needs to be investigated?
Does applying the patch make sense until the issue is fully understood?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-12-07 10:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 11:53 [PATCH] i2c: stm32: Fixes multibyte transfer for STM32F4 I2C controller Radoslaw Pietrzyk
2017-10-12  9:31 ` Pierre Yves MORDRET
2017-10-12  9:55   ` Radosław Pietrzyk
2017-10-17 13:18     ` Pierre Yves MORDRET
2017-10-17 13:51       ` Radosław Pietrzyk
2017-10-17 14:35         ` Pierre Yves MORDRET
2017-10-24 11:45           ` Radosław Pietrzyk
2017-12-07 10:52             ` Wolfram Sang [this message]
2017-12-07 13:23               ` Pierre Yves MORDRET
2017-12-19  8:37                 ` Radosław Pietrzyk

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=20171207105229.jxxyfofsgub27nip@ninjato \
    --to=wsa@the-dreams.de \
    --cc=alexandre.torgue@st.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=pierre-yves.mordret@st.com \
    --cc=radoslaw.pietrzyk@gmail.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;
as well as URLs for NNTP newsgroup(s).