public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Penkler <dpenkler@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	peter.chen@freescale.com, teuniz@gmail.com,
	USB <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 5/5] Add ioctls to enable and disable local controls on an instrument
Date: Wed, 25 Nov 2015 10:12:56 +0100	[thread overview]
Message-ID: <20151125091256.GA1665@slacky> (raw)
In-Reply-To: <CAHp75Vdu0d1pi_okaDSPPYsgG1iq+DzLfQKF+CqrvBcprbbiHA@mail.gmail.com>

On Sun, Nov 22, 2015 at 12:36:53PM +0200, Andy Shevchenko wrote:
> On Sun, Nov 22, 2015 at 10:51 AM, Dave Penkler <dpenkler@gmail.com> wrote:
> > On Wed, Nov 18, 2015 at 11:41:30AM +0200, Andy Shevchenko wrote:
> >> On Wed, Nov 18, 2015 at 10:38 AM, Dave Penkler <dpenkler@gmail.com> wrote:
> 
> 
> >> > +       if (rv < 0) {
> >> > +               dev_err(dev, "simple usb_control_msg failed %d\n", rv);
> >> > +               goto exit;
> >> > +       } else if (rv != 1) {
> >> > +               dev_warn(dev, "simple usb_control_msg returned %d\n", rv);
> >>
> >> Actually here what king of results could be? 0? 2+? In all cases of
> >> error you have to provide an error code.
> >>
> >
> > We seem to be going round in circles here, last time you suggested to
> > propagate the return value.
> 
> You didn't pay much attention to where I put my comment. You have few
> branches depending on return value
> 
> 1) negative, apparently an error code, should be propagated if nothing
> specific to framework;
> 2) zero, what does it means?

Zero bytes transferred -> error

> 3) one, seems the expected result when success, so, error code should be 0;

Which it is when we drop through

> 4) two, three, ??? non-negative numbers,see 2).
> 
> For my understanding 2) and 4) have to return what you initially had -EIO.
> 
> > The non-negative return is the number of bytes
> > transferred which should be 1 unless there is some usb implementation
> > flakiness happening. So I will go back to returning -EIO.
> 
> Yes, in *this* branch.
> 

OK so now I have the same as in v4 again:

	if (rv < 0) {
		dev_err(dev, "simple usb_control_msg failed %d\n", rv);
		goto exit;
	} else if (rv != 1) {
		dev_warn(dev, "simple usb_control_msg returned %d\n", rv);
		rv = -EIO;
		goto exit;
	}

> >
> >> > +               goto exit;
> >> > +       }
> >> > +
> >> > +       if (buffer[0] != USBTMC_STATUS_SUCCESS) {
> >> > +               dev_err(dev, "simple control status returned %x\n", buffer[0]);
> >> > +               rv = -EIO;
> >> > +               goto exit;
> >> > +       }
> >> > +       rv = 0;
> >> > +
> >> > + exit:
> >> > +       kfree(buffer);
> >> > +       return rv;
> >> > +}
> 
> -- 
> With Best Regards,
> Andy Shevchenko

  reply	other threads:[~2015-11-25  9:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18  8:32 [PATCH v5 0/5] usb: usbtmc: Add support for missing functions in USBTMC-USB488 spec Dave Penkler
2015-11-18  8:37 ` [PATCH v5 1/5] Implement an ioctl to support the USMTMC-USB488 READ_STATUS_BYTE operation Dave Penkler
2015-11-18  9:55   ` Andy Shevchenko
2015-11-22  9:19     ` Dave Penkler
2015-11-22 10:32       ` Andy Shevchenko
2015-11-25  9:18         ` Dave Penkler
2015-11-25 20:38           ` Andy Shevchenko
2015-11-28 11:55             ` Dave Penkler
2015-11-28 14:57               ` Andy Shevchenko
2015-11-28 17:41                 ` Dave Penkler
2015-11-28 19:18                   ` Andy Shevchenko
2015-11-18  8:38 ` [PATCH v5 2/5] Add support for USBTMC USB488 SRQ notification with fasync Dave Penkler
2015-11-18  8:38 ` [PATCH v5 3/5] Add support for receiving USBTMC USB488 SRQ notifications via poll/select Dave Penkler
2015-11-18  8:38 ` [PATCH v5 4/5] Add ioctl to retrieve USBTMC-USB488 capabilities Dave Penkler
2015-11-18  8:38 ` [PATCH v5 5/5] Add ioctls to enable and disable local controls on an instrument Dave Penkler
2015-11-18  9:41   ` Andy Shevchenko
2015-11-22  8:51     ` Dave Penkler
2015-11-22 10:36       ` Andy Shevchenko
2015-11-25  9:12         ` Dave Penkler [this message]
2015-11-25 20:46           ` Andy Shevchenko

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=20151125091256.GA1665@slacky \
    --to=dpenkler@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter.chen@freescale.com \
    --cc=teuniz@gmail.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