Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: "Hamilton, Ian" <Ian.Hamilton@xerox.com>
Cc: Greg KH <greg@kroah.com>, Martin Michlmayr <tbm@cyrius.com>,
	Jordan Crouse <jordan.crouse@amd.com>,
	linux-usb-devel@lists.sourceforge.net, linux-mips@linux-mips.org
Subject: Re: [PATCH] Buglet in Alchemy OHCI driver
Date: Tue, 7 Mar 2006 08:54:45 -0800	[thread overview]
Message-ID: <20060307165445.GA6623@suse.de> (raw)
In-Reply-To: <DAF42D2FFC65A146BAB240719E4AD214EE459A@gbrwgceumf02.eu.xerox.net>

On Tue, Mar 07, 2006 at 12:17:21PM -0000, Hamilton, Ian wrote:
> Hi Greg,
> 
> I spotted this in the current latest version of ohci-au1xxx.c (accessed
> via git web interface):
> 
> 94
> 95 		if (dev->resource[1].flags != IORESOURCE_IRQ) {
> 96 		pr_debug ("resource[1] is not IORESOURCE_IRQ");
> 97 		retval -ENOMEM;
> 98 	}
> 99  
> 
> instead this from Martin's patch:
> 
> diff --git a/drivers/usb/host/ohci-au1xxx.c
> b/drivers/usb/host/ohci-au1xxx.c
> index aa4d0cd..d8fb1bb 100644
> --- a/drivers/usb/host/ohci-au1xxx.c
> +++ b/drivers/usb/host/ohci-au1xxx.c
> @@ -94,7 +94,7 @@ int usb_hcd_au1xxx_probe (const struct h
>  
>         if (dev->resource[1].flags != IORESOURCE_IRQ) {
>                 pr_debug ("resource[1] is not IORESOURCE_IRQ");
> -               retval = -ENOMEM;
> +               return -ENOMEM;
>         }
> 
> Line 97 produces a warning, but doesn't stop the build, so may have been
> missed.

Can you check the -mm tree to see if it is fixed there or not?  That has
the patches that are pending from my usb tree in it.

And if not, can you send me a patch against the latest -mm?

thanks,

greg k-h

  parent reply	other threads:[~2006-03-07 16:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07 12:17 [PATCH] Buglet in Alchemy OHCI driver Hamilton, Ian
2006-03-07 12:17 ` Hamilton, Ian
2006-03-07 16:54 ` Greg KH [this message]
2006-03-07 18:28   ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2006-03-01 18:30 Jordan Crouse
2006-03-01 18:37 ` Martin Michlmayr
2006-03-01 23:21   ` Greg KH
2006-03-02 15:33 ` Ralf Baechle
2006-03-02 16:28   ` Greg KH

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=20060307165445.GA6623@suse.de \
    --to=gregkh@suse.de \
    --cc=Ian.Hamilton@xerox.com \
    --cc=greg@kroah.com \
    --cc=jordan.crouse@amd.com \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=tbm@cyrius.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