From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Patches for this merge window
Date: Thu, 21 Mar 2013 10:27:30 -0400 [thread overview]
Message-ID: <20130321142730.GE26945@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ0axi6M_fLS1CaKaQufEEU6DUkpsoSrqEnL2cQpW=R7jw@mail.gmail.com>
On Wed, Mar 20, 2013 at 07:27:24PM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Wed, Mar 20, 2013 at 12:28 PM, Tom Rini <trini@ti.com> wrote:
> > On Sun, Feb 10, 2013 at 09:09:29PM -0800, Simon Glass wrote:
> >
> >> [take 2, sorry]
> >>
> >> Hi Tom,
> >>
> >> I see quite a lot of non-x86 patches in my todo list - does that mean
> >> that I should pick them up if I am happy with them, or just assign
> >> them back to you once I've taken a look?
> >>
> >> I'm keen to get the sandbox fs and memory stuff in fairly early if
> >> possible, since I fear breakages and the longer people have to test
> >> the better. No one has screamed about map_sysmem() but I'm not sure if
> >> anyone noticed. So I could pull these in, build and send a pull if
> >> that suits? Perhaps one series at a time.... Also if Mike is having a
> >> break should I pull in the SPI ones assigned to me?
> >>
> >> There is also buildman, and I'm not sure what to do about that. It
> >> would be nice to have some feedback if people have tried it - I have
> >> had a few private emails only. I think it's a great help, but it still
> >> has some rough edges.
> >
> > Looking back at this, I think only buildman is left. Did all of the
> > other patman related changes get submitted cleanly? I think the answer
> > is we'll take in buildman now so it's easier to get folks to try it in
> > their workflows and see where it takes us.
>
> Yes that's right. I can set up a bundle, along with the patman
> additions, but actually I have found some problems with patman in the
> latest mainline - checkpatch has changed. There are quite a few things
> collected now that need fixing - e.g. Doug's fix to stop removing
> Reviewed-by: tags.
>
> I will start by getting some patches out and we can take a look. Until
> then is it OK to hold off on buildman?
Sounds good to me, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130321/b490ca4e/attachment.pgp>
prev parent reply other threads:[~2013-03-21 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 5:09 [U-Boot] Patches for this merge window Simon Glass
2013-02-11 20:47 ` Tom Rini
2013-02-15 3:41 ` Simon Glass
2013-03-20 19:53 ` Simon Glass
2013-03-20 20:07 ` Tom Rini
2013-04-01 19:01 ` Simon Glass
2013-03-20 19:28 ` Tom Rini
2013-03-21 2:27 ` Simon Glass
2013-03-21 14:27 ` Tom Rini [this message]
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=20130321142730.GE26945@bill-the-cat \
--to=trini@ti.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