Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: Jordan Crouse <jordan.crouse@amd.com>,
	linux-usb-devel@lists.sourceforge.net, linux-mips@linux-mips.org,
	gregkh@suse.de
Subject: Re: [PATCH] Buglet in Alchemy OHCI driver
Date: Wed, 1 Mar 2006 15:21:54 -0800	[thread overview]
Message-ID: <20060301232154.GA13698@kroah.com> (raw)
In-Reply-To: <20060301183735.GA28491@deprecation.cyrius.com>

On Wed, Mar 01, 2006 at 06:37:35PM +0000, Martin Michlmayr wrote:
> * Jordan Crouse <jordan.crouse@amd.com> [2006-03-01 11:30]:
> > Martin Michlmayr spotted this potentially serious bug.  Please apply.
> 
> Please don't send patches as MIME attachments.  Here it is again (with
> a better summary too):
> 
> 
> [PATCH] Alchemy OCHI: return if right resources cannot be obtained
> 
> From: Jordan Crouse <jordan.crouse@amd.com>
> 
> Failure to get the right resources should immediately return.  Current
> code has the possiblity of running off into the weeds. Spotted by
> Martin Michlmayr.
> 
> Signed-off-by: Jordan Crouse <jordan.crouse@amd.com>
> Signed-off-by: Martin Michlmayr <tbm@cyrius.com>

This patch is already in my tree, in the other patch from Jordan, so it
will make it in after 2.6.16-final is out.

thanks,

greg k-h

  reply	other threads:[~2006-03-01 23:14 UTC|newest]

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

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=20060301232154.GA13698@kroah.com \
    --to=greg@kroah.com \
    --cc=gregkh@suse.de \
    --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