devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Codrin.Ciubotariu@microchip.com>
To: <robh@kernel.org>
Cc: <linux-i2c@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <kamel.bouhara@bootlin.com>,
	<wsa@the-dreams.de>, <Nicolas.Ferre@microchip.com>,
	<alexandre.belloni@bootlin.com>,
	<Ludovic.Desroches@microchip.com>
Subject: Re: [PATCH v2 1/6] dt-bindings: i2c: at91: document optional bus recovery properties
Date: Mon, 6 Jan 2020 16:34:51 +0000	[thread overview]
Message-ID: <5f7c19f6-014e-d207-d3ab-bb439e1847f8@microchip.com> (raw)
In-Reply-To: <20200103222919.GA32421@bogus>

On 04.01.2020 00:29, Rob Herring wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On Fri, 3 Jan 2020 09:49:06 +0000, <Codrin.Ciubotariu@microchip.com> wrote:
>>
>> From: Kamel Bouhara <kamel.bouhara@bootlin.com>
>>
>> The at91 I2C controller can support bus recovery by re-assigning SCL
>> and SDA to gpios. Add the optional pinctrl and gpio properties to do
>> so.
>>
>> Signed-off-by: Kamel Bouhara <kamel.bouhara@bootlin.com>
>> ---
>>
>> Changes in v2:
>>   - none
>>
>>   Documentation/devicetree/bindings/i2c/i2c-at91.txt | 10 ++++++++++
>>   1 file changed, 10 insertions(+)
>>
> 
> Please add Acked-by/Reviewed-by tags when posting new versions. However,
> there's no need to repost patches *only* to add the tags. The upstream
> maintainer will do that for acks received on the version they apply.
> 
> If a tag was not added on purpose, please state why and what changed.
> 

Sorry Rob, I forgot to add your Acked-by. There is nothing changed in 
this version. How should I proceed, should I resend it with your tag?

Best regards,
Codrin

  reply	other threads:[~2020-01-06 16:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03  9:49 [PATCH v2 0/6] i2c bus recovery for Microchip SoCs Codrin.Ciubotariu
2020-01-03  9:49 ` [PATCH v2 1/6] dt-bindings: i2c: at91: document optional bus recovery properties Codrin.Ciubotariu
2020-01-03 22:29   ` Rob Herring
2020-01-06 16:34     ` Codrin.Ciubotariu [this message]
2020-01-03  9:49 ` [PATCH v2 2/6] i2c: at91: implement i2c bus recovery Codrin.Ciubotariu
2020-01-09  7:48   ` Ludovic Desroches
2020-01-09 10:54     ` Codrin.Ciubotariu
2020-01-03  9:49 ` [PATCH v2 3/6] i2c: at91: Send bus clear command if SCL is down Codrin.Ciubotariu
2020-01-09  7:47   ` Ludovic Desroches
2020-01-09 10:58     ` Codrin.Ciubotariu
2020-01-09 11:05   ` Russell King - ARM Linux admin
2020-01-09 13:29     ` Codrin.Ciubotariu
2020-01-03  9:49 ` [PATCH v2 5/6] ARM: at91/dt: sama5d4: add i2c gpio pinctrl Codrin.Ciubotariu
2020-01-03  9:49 ` [PATCH v2 4/6] ARM: at91/dt: sama5d3: " Codrin.Ciubotariu
2020-01-04 22:39   ` Peter Rosin
2020-01-06 16:58     ` Codrin.Ciubotariu
2020-01-03  9:49 ` [PATCH v2 6/6] ARM: at91/dt: sama5d2: " Codrin.Ciubotariu

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=5f7c19f6-014e-d207-d3ab-bb439e1847f8@microchip.com \
    --to=codrin.ciubotariu@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kamel.bouhara@bootlin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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 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).