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] [PATCH V2 1/4] arm: mx5: Fix memory slowness on MX53QSB
Date: Mon, 31 Mar 2014 11:52:38 +0200	[thread overview]
Message-ID: <201403311152.38532.marex@denx.de> (raw)
In-Reply-To: <533939A2.8080901@denx.de>

On Monday, March 31, 2014 at 11:47:14 AM, Stefano Babic wrote:
> Hi Marek,
> 
> On 31/03/2014 09:48, Marek Vasut wrote:
> > Thanks :)
> > 
> > There are a few more patches in your PW queue from me, please check them
> > and apply as seen fit. Thanks again!
> 
> All patches from you (or from others) that are ok for me and ready to be
> merged are marked by me in PW as "under reviewed" - there is not a
> "review passed " or "ready-to-be-merged" status. You can check yourself
> if some of your patches are missing.

Will do, but I think you got them all. Thanks!

Best regards,
Marek Vasut

  reply	other threads:[~2014-03-31  9:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28  7:30 [U-Boot] [PATCH V2 1/4] arm: mx5: Fix memory slowness on MX53QSB Marek Vasut
2014-03-28  7:30 ` [U-Boot] [PATCH V3 2/4] arm: mx5: Avoid hardcoding memory sizes " Marek Vasut
2014-04-01  8:19   ` Stefano Babic
2014-03-28  7:31 ` [U-Boot] [PATCH V2 3/4] arm: mx5: Fix memory slowness on M53EVK Marek Vasut
2014-04-01  8:20   ` Stefano Babic
2014-03-28  7:31 ` [U-Boot] [PATCH V3 4/4] arm: mx5: Avoid hardcoding memory sizes " Marek Vasut
2014-04-01  8:20   ` Stefano Babic
2014-03-31  7:21 ` [U-Boot] [PATCH V2 1/4] arm: mx5: Fix memory slowness on MX53QSB Stefano Babic
2014-03-31  7:48   ` Marek Vasut
2014-03-31  9:47     ` Stefano Babic
2014-03-31  9:52       ` Marek Vasut [this message]
2014-04-01  8:19 ` Stefano Babic

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=201403311152.38532.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