Linux USB
 help / color / mirror / Atom feed
From: Ladislav Michl <ladis@linux-mips.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [v3] usb: ehci-omap: don't complain on -EPROBE_DEFER when no PHY found
Date: Thu, 18 Jan 2018 16:26:13 +0100	[thread overview]
Message-ID: <20180118152613.GA22493@lenoch> (raw)

On Thu, Jan 18, 2018 at 10:18:41AM -0500, Alan Stern wrote:
> On Thu, 18 Jan 2018, Ladislav Michl wrote:
> 
> > Don't complain on -EPROBE_DEFER when no PHY found, the driver
> > probe will be retried later.
> > 
> > Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> > Acked-by: Tony Lindgren <tony@atomide.com>
> > Acked-by: Roger Quadros <rogerq@ti.com>
> > ---
> >  Changes:
> >  - v2: None, just added Tony's ack
> >  - v3: Fixed commit message typo spotted by Jaejoong Kim, added Roger's ack
> 
> Although there's nothing wrong with making this change, people don't 
> like to see character strings broken up just to avoid long lines.  Can 
> you redo the patch without breaking the error message string?

Sure I could, but I broke that long line intentionaly. Line lenght rule is
normally broken for string just to allow people grepping for error message in
source files and I guess everyone sane would grep for "Can't get PHY device for
port" which is on single line. So this way we:
1) respect 80 chars limit
2) have error message grepable.

Do you still insist on making this one long line? (I have no problem sending
v4, just wanted to give some rationale before I eventually do so)

Best regards,
	ladis

> >  drivers/usb/host/ehci-omap.c | 5 +++--
> >  1 file changed, 3 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/usb/host/ehci-omap.c b/drivers/usb/host/ehci-omap.c
> > index 854b146a457d..fd6170962a1a 100644
> > --- a/drivers/usb/host/ehci-omap.c
> > +++ b/drivers/usb/host/ehci-omap.c
> > @@ -167,8 +167,9 @@ static int ehci_hcd_omap_probe(struct platform_device *pdev)
> >  				continue;
> >  
> >  			ret = PTR_ERR(phy);
> > -			dev_err(dev, "Can't get PHY device for port %d: %d\n",
> > -					i, ret);
> > +			if (ret != -EPROBE_DEFER)
> > +				dev_err(dev, "Can't get PHY device for port "
> > +					"%d: %d\n", i, ret);
> >  			goto err_phy;
> >  		}
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2018-01-18 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 15:26 Ladislav Michl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-01-18 18:50 [v3] usb: ehci-omap: don't complain on -EPROBE_DEFER when no PHY found Alan Stern
2018-01-18 15:18 Alan Stern
2018-01-18  8:04 Ladislav Michl

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=20180118152613.GA22493@lenoch \
    --to=ladis@linux-mips.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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