From: Roland Stigge <stigge@antcom.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: grant.likely@secretlab.ca, robherring2@gmail.com,
vitalywool@gmail.com, khali@linux-fr.org, ben-linux@fluff.org,
rob.herring@calxeda.com, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org, kevin.wells@nxp.com,
Srinivas Bakki <srinivas.bakki@nxp.com>
Subject: Re: [PATCH v5] i2c: Add device tree support to i2c-pnx.c
Date: Fri, 20 Apr 2012 15:14:46 +0200 [thread overview]
Message-ID: <4F916146.1080904@antcom.de> (raw)
In-Reply-To: <20120420120950.GA15613@pengutronix.de>
Hi,
On 04/20/2012 02:09 PM, Wolfram Sang wrote:
>> Signed-off-by: Roland Stigge <stigge@antcom.de> Reviewed-by: Arnd
>> Bergmann <arnd@arndb.de> Acked-by: Wolfram Sang
>> <w.sang@pengutronix.de>
>
> NACK! I said the approach of dropping "timeout" is OK, but unless I
> say "you may add my ack after changing this and that", please do
> not automatically add my ack. Doesn't hurt here, since I have to
> pick it up anyway.
Sorry - my apologies! Removing for next re-post.
>> Changes since v4: * Removed OF timeout property (to be added
>> later when there is consensus about how to call and handle it) *
>> Changed clock-frequency example to decimal
>
> Thanks, I just noticed. Please drop (more precise: remove) the
> "slave-addr" for the same reasons as "timeout".
OK, will do.
>> ret = request_irq(alg_data->irq, i2c_pnx_interrupt, - 0,
>> pdev->name, alg_data); + 0, pdev->name, alg_data);
>
> I know that checkpatch complains about this, but I'd prefer to
> avoid such changes unless the code before was really unreadable.
OK!
Roland
prev parent reply other threads:[~2012-04-20 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 9:22 [PATCH v5] i2c: Add device tree support to i2c-pnx.c Roland Stigge
2012-04-20 12:09 ` Wolfram Sang
2012-04-20 13:14 ` Roland Stigge [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=4F916146.1080904@antcom.de \
--to=stigge@antcom.de \
--cc=arm@kernel.org \
--cc=ben-linux@fluff.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=kevin.wells@nxp.com \
--cc=khali@linux-fr.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.com \
--cc=srinivas.bakki@nxp.com \
--cc=vitalywool@gmail.com \
--cc=w.sang@pengutronix.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