linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] i2c: mv64xxx: Fix transfer error code
Date: Tue, 25 Jun 2013 18:42:58 +0200	[thread overview]
Message-ID: <20130625164258.GB2973@katana> (raw)
In-Reply-To: <20130621001627.GA25889-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>

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

On Thu, Jun 20, 2013 at 05:16:27PM -0700, Guenter Roeck wrote:
> On Thu, Jun 20, 2013 at 09:23:37PM +0200, Wolfram Sang wrote:
> > On Wed, Jun 19, 2013 at 02:53:52PM -0700, Guenter Roeck wrote:
> > > The driver returns -ENODEV as error code if it did not get an ACK
> > > from the device. Per Documentation/i2c/fault-codes, it should
> > > return -ENXIO.
> > > 
> > > Signed-off-by: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
> > 
> > Thanks, have you checked the other error codes as well while you were
> > there?
> > 
> Other error codes are ok as far as I can see.

Applied to for-next, thanks for double checking!

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

      parent reply	other threads:[~2013-06-25 16:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 21:53 [PATCH] i2c: mv64xxx: Fix transfer error code Guenter Roeck
     [not found] ` <1371678832-26889-1-git-send-email-linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2013-06-20 19:23   ` Wolfram Sang
2013-06-20 21:12     ` Guenter Roeck
2013-06-21  0:16     ` Guenter Roeck
     [not found]       ` <20130621001627.GA25889-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2013-06-25 16:42         ` 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=20130625164258.GB2973@katana \
    --to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
    --cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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).