All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: engidudu <usbhc_dev@nergal.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SL811HS driver
Date: Tue, 25 Feb 2003 09:39:15 -0800	[thread overview]
Message-ID: <20030225173914.GD8648@kroah.com> (raw)
In-Reply-To: <004501c2dcf0$8e2757c0$570610ac@pclab1>

On Tue, Feb 25, 2003 at 06:08:45PM +0100, engidudu wrote:
> Hi,
> 
> we have modified the linux driver for SL811 USB HOST Controller by CYPRESS.
> We have improved the program's flow:
> - interrupt handler,
> - double buffering.
> It works well during writing transactions, but we still have problems
> implementing
> double buffering during reading transactions.
> We would like to send you our source code to attend the next kernel release.
> These codes work on uClinux (kernel 2.4) too.
> 
> How do we have to send these codes?

Please read Documentation/SubmittingPatches and then send the patch to
me and the linux-usb-devel mailing list.  You can also copy linux-kernel
if you really want to.

thanks,

greg k-h

      reply	other threads:[~2003-02-25 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25 17:08 SL811HS driver engidudu
2003-02-25 17:39 ` Greg KH [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=20030225173914.GD8648@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=usbhc_dev@nergal.it \
    /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.