public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] usb:udc: Remove duplicated USB definitions from include/linux/usb/ch9.h file
Date: Thu, 12 Apr 2012 11:06:58 +0200	[thread overview]
Message-ID: <20120412110658.37ca0286@lmajewski.digital.local> (raw)
In-Reply-To: <201204121008.59159.marex@denx.de>


Hi Marek,

> Dear Lukasz Majewski,
> 
> > Remove the repeated USB descriptor code and use usbdescriptors.h
> > file. ch9.h file has been copied from linux and is needed for USB
> > gadget related work.
> > Now usbdescriptors.h and ch9.h shall be used together.


> 
> Please don't expect my response on these patches earlier than in 2
> days time -- I have a slow build-test machine. Also, I'll be
> eventually scheduling these for next release, ok?

I think that good testing is welcome, since <usbstrings.h> and <ch9.h>
are used widely (up to now separately) in USB. It can be submitted for
-rc or next release. It depends if we manage to test it thoroughly.

BTW: Can you share information how could I get toolchains for mips,
powerPC to test more architectures from MAKEALL script?

Do you use ELDK 5.1 or any "customized" toolchain?
I'm planning to setup some build server.

> 
> Though I'll likely review these today.

Great.
> 
> btw. this patch looks reasonable, but I'll need to build-test it .
> 


-- 
Best regards,

Lukasz Majewski

Samsung Poland R&D Center
Platform Group

  reply	other threads:[~2012-04-12  9:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12  7:10 [U-Boot] [PATCH] usb:udc: Remove duplicated USB definitions from include/linux/usb/ch9.h file Lukasz Majewski
2012-04-12  8:08 ` Marek Vasut
2012-04-12  9:06   ` Lukasz Majewski [this message]
2012-04-14  9:42 ` Marek Vasut

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=20120412110658.37ca0286@lmajewski.digital.local \
    --to=l.majewski@samsung.com \
    --cc=u-boot@lists.denx.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