From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Horman <horms+renesas@verge.net.au>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Chris Brandt <chris.brandt@renesas.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Magnus Damm <magnus.damm@gmail.com>,
Linux I2C <linux-i2c@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 2/4] dt-bindings: i2c: rcar: Rename bindings documentation file
Date: Fri, 2 Aug 2019 15:36:56 +0200 [thread overview]
Message-ID: <20190802133656.GA23542@kunai> (raw)
In-Reply-To: <CAMuHMdUYTo1_zz4sCv5=PRL90EyFSU_b5WgUJoc4Oii08F_tww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
Hi Geert,
> With the above fixed:
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Now I understand why I applied this patch despite your request for a
change. Patchwork picked up the tag, and so I it looked to me in the
patchwork summary that this patch series was completely reviewed.
Would it be OK for you to not give the formal tag in advance but rather
describe it like "you may add my rev-by tag like in patch 1"? Or just
wait for v2 and tag?
Workflows aside, thanks for your continued reviews of patches!
Best regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-08-02 13:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 12:15 [PATCH 0/4] dt-bindings: i2c: renesas: Rename bindings documentation files Simon Horman
2019-07-24 12:15 ` [PATCH 1/4] dt-bindings: i2c: sh_mobile: Rename bindings documentation file Simon Horman
2019-07-29 11:39 ` Geert Uytterhoeven
2019-07-24 12:15 ` [PATCH 2/4] dt-bindings: i2c: rcar: " Simon Horman
2019-07-29 11:42 ` Geert Uytterhoeven
2019-08-02 13:36 ` Wolfram Sang [this message]
2019-07-24 12:15 ` [PATCH 3/4] dt-bindings: i2c: riic: " Simon Horman
2019-07-29 11:43 ` Geert Uytterhoeven
2019-07-24 12:15 ` [PATCH 4/4] " Simon Horman
2019-07-29 11:46 ` Geert Uytterhoeven
2019-08-01 12:57 ` [PATCH 0/4] dt-bindings: i2c: renesas: Rename bindings documentation files Wolfram Sang
2019-08-02 9:27 ` Geert Uytterhoeven
2019-08-02 10:02 ` 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=20190802133656.GA23542@kunai \
--to=wsa@the-dreams.de \
--cc=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).