All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: Felipe Balbi <balbi@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [RFC PATCH] usb: gadget: Introduce Cadence USB2 UDC Driver
Date: Tue, 24 May 2016 18:35:34 +0300	[thread overview]
Message-ID: <1749484.hlG8oPefGN@avalon> (raw)
In-Reply-To: <57446230.6000208@baylibre.com>

Hi Neil,

On Tuesday 24 May 2016 16:16:16 Neil Armstrong wrote:
> Hi Felipe, Laurent,
> 
> I submitted this driver for a Cadence IP library from a now abandoned
> project.
> 
> The driver was working on a SoC platform ported on a FPGA, but I do not have
> access to this HW anymore.
> 
> But I have a fixed version...
> 
> Now, I am looking for SoCs, vendors and even Cadence people (or even
> Evatronix employees who worked on this IP before being in Cadence
> portfolio) to push this driver upstream by testing it on a real HW or even
> FPGA.
> 
> I hope this message in a bottle will get read !

I've read it, but what do you expect from me ? :-)

-- 
Regards,

Laurent Pinchart

      parent reply	other threads:[~2016-05-24 15:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 16:33 [RFC PATCH] usb: gadget: Introduce Cadence USB2 UDC Driver kbuild test robot
2015-10-16 14:54 ` Neil Armstrong
2015-10-16 16:33   ` [PATCH] usb: gadget: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-10-16 16:33   ` [PATCH] usb: gadget: fix bugon.cocci warnings kbuild test robot
2015-10-16 16:46   ` [RFC PATCH] usb: gadget: Introduce Cadence USB2 UDC Driver kbuild test robot
2015-11-16 16:11   ` Felipe Balbi
2016-05-24 14:16     ` Neil Armstrong
2016-05-24 14:34       ` Felipe Balbi
2016-05-24 15:35       ` Laurent Pinchart [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=1749484.hlG8oPefGN@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=narmstrong@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.