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] Weekly status
Date: Mon, 17 Sep 2012 19:50:23 +0200	[thread overview]
Message-ID: <201209171950.24012.marex@denx.de> (raw)
In-Reply-To: <20120917143132.GA31809@bill-the-cat>

Dear Tom Rini,

> Hey all,
> 
> I had intended to send this last thing Friday but it slipped my mind.
> But with my intention to do -rc1 this Friday, this works too.  That
> said...
> 
> Here's where I'm at so far:
> - Locally, I believe I have all outstanding pull requets queued up and
>   MAKEALL'd when there's an ELDK toolchain.

You're getting them MAKEALL's around 6 hours after you push it to master for PPC 
and ARM with ELDK4.2 and 5.2 ;-)

> - Working out the access issues with Detlev.
> - I've given the first two pages of patchwork a read and assign pass.
>   If you're a custodian I've probably assigned a few patches to you that
>   look like your area.  I've also done my best to spot superseded
>   patches and things which have been accepted but I'm sure I missed a
>   few.
> - If you have assigned me items in patchwork and sent me an email, I
>   have read it and will act on it shortly if I haven't already (just
>   don't want the queue of "I have applied this" messages locally to get
>   too large).

I think I have a few more USB patches holed up in my usb tree, I'll send you a 
pullRQ now.

> I expect to be able to snap -rc1 on my previously announced schedule.
> Once I do the usual rules about next will open and I would encourage
> custodians to open up a next branch as well.

Best regards,
Marek Vasut

  reply	other threads:[~2012-09-17 17:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17 14:31 [U-Boot] Weekly status Tom Rini
2012-09-17 17:50 ` Marek Vasut [this message]
2012-09-18 15:03 ` Tom Rini

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