devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Nicholas Mc Guire <der.herr@hofr.at>
Cc: Grant Likely <grant.likely@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Yao Yuan <yao.yuan@freescale.com>,
	Fugang Duan <B38611@freescale.com>,
	Fabio Estevam <fabio.estevam@freescale.com>,
	Jingoo Han <jg1.han@samsung.com>,
	Kaushal Butala <kaushalkernelmailinglist@gmail.com>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 -next] i2c: imx: fix handling of wait_for_completion_timeout result
Date: Tue, 13 Jan 2015 16:16:02 +0100	[thread overview]
Message-ID: <20150113151601.GI7660@katana> (raw)
In-Reply-To: <1419687233-10498-1-git-send-email-der.herr@hofr.at>

[-- Attachment #1: Type: text/plain, Size: 648 bytes --]

On Sat, Dec 27, 2014 at 08:33:53AM -0500, Nicholas Mc Guire wrote:
> wait_for_completion_timeout does not return negative values so 
> "result" handling here should be simplified to cover the actually
> possible cases only.
> 
> patch was only compile tested for imx_v6_v7_defconfig 
> 
> V2 spellchecked this time and proper labeling as 
>    suggested by Sedat Dilek <sedat.dilek@gmail.com>
> 
> patch is against linux-next 3.19.0-rc1 -next-20141226 

The last two paragraphs should have been below "---" but other than
that, all is OK.

> 
> Signed-off-by: Nicholas Mc Guire <der.herr@hofr.at>

Applied to for-next, thanks!


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-01-13 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-27 13:33 [PATCH v2 -next] i2c: imx: fix handling of wait_for_completion_timeout result Nicholas Mc Guire
2015-01-13 15:16 ` Wolfram Sang [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=20150113151601.GI7660@katana \
    --to=wsa@the-dreams.de \
    --cc=B38611@freescale.com \
    --cc=der.herr@hofr.at \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@freescale.com \
    --cc=grant.likely@linaro.org \
    --cc=jg1.han@samsung.com \
    --cc=kaushalkernelmailinglist@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=yao.yuan@freescale.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).