public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: Felipe Balbi <balbi@ti.com>
Cc: Michael Jones <michael.jones@matrix-vision.de>,
	linux-omap@vger.kernel.org
Subject: Re: double_buffer_not_ok compile error
Date: Thu, 24 Feb 2011 13:31:59 +0000	[thread overview]
Message-ID: <20110224133159.GA28332@Eternity> (raw)
In-Reply-To: <20110221135613.GF23087@legolas.emea.dhcp.ti.com>

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

On Mon, Feb 21, 2011 at 03:56:13PM +0200, Felipe Balbi wrote:
> On Mon, Feb 21, 2011 at 02:54:27PM +0100, Michael Jones wrote:
> > Hi Felipe,
> > 
> > Sorry, thanks.  I tried to avoid getting that reply by searching the
> > mailing list to see whether this was already discovered.  I searched for
> > "double_buffer_not_ok" and "musb_host" on the mailing list but didn't
> > see anything newer than the original patch.
> > 
> > Where is the correct place to search for such a recent fix?  Where is
> > Greg's queue?
> 
> Yes, Greg's usb-linux or my gitorious musb branch.
> 
> -- 
> balbi
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hi, thanks for that. Ran into the same problem whilst trying the
linux-linaro-2.6.38 tree. I hope your patch will make it to this tree
soon

Regards,
-- 
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2

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

      reply	other threads:[~2011-02-24 13:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 12:59 double_buffer_not_ok compile error Michael Jones
2011-02-21 13:25 ` Felipe Balbi
2011-02-21 13:54   ` Michael Jones
2011-02-21 13:56     ` Felipe Balbi
2011-02-24 13:31       ` Markos Chandras [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=20110224133159.GA28332@Eternity \
    --to=hwoarang@gentoo.org \
    --cc=balbi@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=michael.jones@matrix-vision.de \
    /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