From: Ray Jui <rjui@broadcom.com>
To: Wolfram Sang <wsa@the-dreams.de>,
"Jayachandran C." <jchandra@broadcom.com>
Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
"Kumar Gala <galak@codeaurora.org>,
Grant Likely <grant.likely@linaro.org>,
Subhendu Sekhar Behera" <sbehera@broadcom.com>
Subject: Re: [PATCH 2/2] i2c: Support for Netlogic XLP9XX/5XX I2C controller.
Date: Mon, 9 Feb 2015 21:27:08 -0800 [thread overview]
Message-ID: <54D996AC.3000405@broadcom.com> (raw)
In-Reply-To: <20150209172301.GA11749@katana>
On 2/9/2015 9:23 AM, Wolfram Sang wrote:
>
>> Given that we have already have i2c/busses/i2c-xlr.c upstream (and updates
>> to i2c-ocores.c for our earlier chip), I was hoping that we have got things
>> right this time.
>
> From the glimpse I had, it was mostly OK. Yet, a number of nits in
> regard to API updates, superfluous things. Stuff like that.
>
> You could also check earlier reviews from me and check if there are
> issues which apply to your driver as well.
>
>> Anyway, I will forward it internally to Ray for review, and if necessary
>> submit another patch.
>
> Thanks!
>
Yes, I'll help to review it. Thanks!
Ray
prev parent reply other threads:[~2015-02-10 5:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 7:23 [PATCH 1/2] of: Add vendor prefix 'netlogic' Jayachandran C
[not found] ` <1421393020-18807-1-git-send-email-jchandra-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-01-16 7:23 ` [PATCH 2/2] i2c: Support for Netlogic XLP9XX/5XX I2C controller Jayachandran C
[not found] ` <1421393020-18807-2-git-send-email-jchandra-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2015-02-09 15:28 ` Wolfram Sang
2015-02-09 16:15 ` Jayachandran C.
[not found] ` <20150209161549.GA2787-l4W0uAg2RDvWG0bvociYJ/An/qbn1+6FOui0OUZsNXA@public.gmane.org>
2015-02-09 17:23 ` Wolfram Sang
2015-02-10 5:27 ` Ray Jui [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=54D996AC.3000405@broadcom.com \
--to=rjui@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jchandra@broadcom.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sbehera@broadcom.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).