All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Liu <jim.t90615@gmail.com>
To: Marek Vasut <marex@denx.de>
Cc: aford173@gmail.com, sjg@chromium.org,
	Stanley Chu <YSCHU@nuvoton.com>,
	 KWLIU@nuvoton.com, Jim Liu <JJLIU0@nuvoton.com>,
	u-boot@lists.denx.de
Subject: Re: [PATCH v1] usb: host: nuvoton: Add nuvoton NPCM7xx ehci/ohci driver
Date: Tue, 28 Jun 2022 11:49:53 +0800	[thread overview]
Message-ID: <CAKUZ0+FZw9SUB0d6GmNRkxxG9+M=0MgvfzNjVNGU=FBsUDQmiw@mail.gmail.com> (raw)
In-Reply-To: <f4a94438-ba34-8c81-3197-180122fe82ae@denx.de>

Hi Marek

Thank you for your reminder.
Dell is use novuton uboot git repo now.
and request us upstream it.

npcm7xx normal defconfig is poleg_evb_defconfig, so all people use
this config to build uboot.
and poleg_evb_defconfig is in uboot master now.

I separate all the drivers to several commits,after I modify each
driver coding style.
and the poleg_evb_defconfig will be updated in the last commit

When the upstream task is finished , Dell or others will use upstream uboot.

If you have any suggestions please let me know.


On Mon, Jun 27, 2022 at 5:31 PM Marek Vasut <marex@denx.de> wrote:
>
> On 6/27/22 07:30, Jim Liu wrote:
> > Hi Marek
>
> Hello all,
>
> > Thanks for your reply.
> > The answer is yes.
> > Our customer Dell is using our driver now.
> > so need upstream uboot source to uboot master.
>
> All right, so this Dell device is also going to be upstreamed then ?
>
> If the driver is just going to be upstream and never enabled, it would
> bitrot and be useless -- that's my concern.

  reply	other threads:[~2022-06-28  3:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21  9:09 [PATCH v1] usb: host: nuvoton: Add nuvoton NPCM7xx ehci/ohci driver Jim Liu
2022-06-24 18:11 ` Marek Vasut
2022-06-27  5:30   ` Jim Liu
2022-06-27  9:31     ` Marek Vasut
2022-06-28  3:49       ` Jim Liu [this message]
2022-06-28  9:39         ` Marek Vasut
2022-06-29  1:31           ` Jim Liu
2022-06-29  9:23             ` 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='CAKUZ0+FZw9SUB0d6GmNRkxxG9+M=0MgvfzNjVNGU=FBsUDQmiw@mail.gmail.com' \
    --to=jim.t90615@gmail.com \
    --cc=JJLIU0@nuvoton.com \
    --cc=KWLIU@nuvoton.com \
    --cc=YSCHU@nuvoton.com \
    --cc=aford173@gmail.com \
    --cc=marex@denx.de \
    --cc=sjg@chromium.org \
    --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 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.