public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request: u-boot-dfu
Date: Thu, 8 May 2014 12:12:09 +0200	[thread overview]
Message-ID: <201405081212.09473.marex@denx.de> (raw)
In-Reply-To: <20140508090824.68f6d65b@amdc2363>

On Thursday, May 08, 2014 at 09:08:24 AM, Lukasz Majewski wrote:
> Hi Heiko,
> 
> > Hello Lukasz,
> > 
> > Am 08.05.2014 08:30, schrieb Lukasz Majewski:
> > > Hi Marek,
> > > 
> > >> On Tuesday, May 06, 2014 at 11:29:32 AM, Lukasz Majewski wrote:
> > >>> Hi Marek,
> > >>> 
> > >>> The following changes since commit
> > >>> 
> > >>> af41d6b4cb1602abebaaa9c8774a9b0ece564796:
> > >>>    common: fixed linker-list example (2014-05-05 10:24:13 +0200)
> > >>> 
> > >>> are available in the git repository at:
> > >>>    ssh://gu-dfu at git.denx.de/u-boot-dfu master
> > >>> 
> > >>> for you to fetch changes up to
> > >>> 
> > >>> c805776ce7079c7b7dd54c644b499e1b8f6296b1:
> > >>>    ums: allow the user to specify the device type (2014-05-06
> > >>> 
> > >>> 11:13:23 +0200)
> > >>> 
> > >>> ----------------------------------------------------------------
> > >>> 
> > >>> Stephen Warren (9):
> > >>>        usb: ums: add error handling for failed registration
> > >>>        ums: support block devices not MMC devices
> > >>>        ums: remove UMS_{NUM,START}_SECTORS + UMS_START_SECTOR
> > >>>        ums: remove error-checking of MMC device size
> > >>>        ums: remove ums_disk_init()
> > >>>        ums: move IO support code to common location
> > >>>        ums: use get_device() not find_mmc_device();
> > >>>        ums: move all variable declarations to the start of the
> > >>> 
> > >>> block ums: allow the user to specify the device type
> > >> 
> > >> This doesn't match what's in U-Boot-dfu.git/master [1] it seems. Or
> > >> does it ... ?
> > > 
> > > This PR seems outdated :-).
> > > 
> > > I've also added to u-boot-dfu work done Rob Herring in the meantime.
> > > 
> > > I will prepare new PR with those changes included.
> > > Thanks for pointing out.
> > 
> > Hmm, I have 2 patches pending ...
> > 
> > [U-Boot,1/2] musb-new, dfu: first send request answer then call
> > completions http://patchwork.ozlabs.org/patch/337982/
> > 
> > and
> > 
> > [U-Boot,v2] dfu, nand: add medium specific polltimeout function
> > http://patchwork.ozlabs.org/patch/338369/
> > 
> > Could you (or Marek) add them? Or are there some issues with them?
> 
> I will test them and if no regressions appear I will add them to
> u-boot-dfu tree.

Thanks.

Best regards,
Marek Vasut

  reply	other threads:[~2014-05-08 10:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06  9:29 [U-Boot] Pull request: u-boot-dfu Lukasz Majewski
2014-05-07 21:38 ` Marek Vasut
2014-05-08  6:30   ` Lukasz Majewski
2014-05-08  6:46     ` Heiko Schocher
2014-05-08  7:08       ` Lukasz Majewski
2014-05-08 10:12         ` Marek Vasut [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-08  8:56 Lukasz Majewski
2014-05-08 13:04 ` Marek Vasut
2014-05-05  8:27 Lukasz Majewski
2014-05-05  9:52 ` 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=201405081212.09473.marex@denx.de \
    --to=marex@denx.de \
    --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