From: Sekhar Nori <nsekhar@ti.com>
To: Pascal Huerst <pascal.huerst@gmail.com>, wsa@the-dreams.de
Cc: tony@atomide.com, linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH v3] i2c: omap: Add calls for pinctrl state select
Date: Wed, 6 May 2015 17:03:55 +0530 [thread overview]
Message-ID: <5549FC23.1010704@ti.com> (raw)
In-Reply-To: <5549F84A.50206@gmail.com>
On Wednesday 06 May 2015 04:47 PM, Pascal Huerst wrote:
> Sekhar Nori, any objections on that version?
None. FWIW, you can add:
Reviewed-by: Sekhar Nori <nsekhar@ti.com>
Thanks,
Sekhar
prev parent reply other threads:[~2015-05-06 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 11:19 [PATCH v3] i2c: omap: Add calls for pinctrl state select pascal.huerst-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <1430219973-24260-1-git-send-email-pascal.huerst-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-06 11:17 ` Pascal Huerst
2015-05-06 11:33 ` Sekhar Nori [this message]
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=5549FC23.1010704@ti.com \
--to=nsekhar@ti.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pascal.huerst@gmail.com \
--cc=tony@atomide.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).