From: Pierre Yves MORDRET <pierre-yves.mordret@st.com>
To: "Wolfram Sang" <wsa@the-dreams.de>,
"Radosław Pietrzyk" <radoslaw.pietrzyk@gmail.com>
Cc: 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 14:23:52 +0100 [thread overview]
Message-ID: <dae4399e-4209-b052-a4c0-8a11c17ce032@st.com> (raw)
In-Reply-To: <20171207105229.jxxyfofsgub27nip@ninjato>
I do believe some investigation has to be done prior merging this patch.
The impact is genuine and has to be tested thoroughly before granting an ack.
Thus I prefer having a better understanding of the issue.
I will try to work on this later on.
Regards
On 12/07/2017 11:52 AM, Wolfram Sang wrote:
> 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?
>
next prev parent reply other threads:[~2017-12-07 13:23 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
2017-12-07 13:23 ` Pierre Yves MORDRET [this message]
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=dae4399e-4209-b052-a4c0-8a11c17ce032@st.com \
--to=pierre-yves.mordret@st.com \
--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=radoslaw.pietrzyk@gmail.com \
--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 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).