All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sinan Akman <sinan@writeme.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2015.04-rc1 released
Date: Mon, 02 Feb 2015 17:03:59 -0500	[thread overview]
Message-ID: <54CFF44F.6020908@writeme.com> (raw)
In-Reply-To: <20150202190012.GQ10826@bill-the-cat>

   Hi Tom

On 02/02/2015 02:00 PM, Tom Rini wrote:
> Hey all,
>
> I've pushed v2015.04-rc1 out to the repository and tarballs should exist
> soon.

   I had this short patch sent out some time ago :

http://u-boot.10912.n7.nabble.com/PATCH-mpc837xerdb-fix-Calling-hwconfig-without-a-buffer-warning-tp202599.html

   I am new to the process and I wonder if all the mpc83xx
related patches need to go through Kim or if self-contained
(specific to a board) patches could be picked up by you. I feel
Kim is little too busy for this.

   I have few other related patches prepared that I would like
to send.

   I also sent out this e-mail to Ilya for another generic
board support :

http://u-boot.10912.n7.nabble.com/mpc8308rdb-generic-board-support-tc203974.html

   I have patches for mpc8323rdb to add generic board support
and that it doesn't get removed. It is known to be not maintained
and I can maintain that board as well. (prev maintainer
Michael Barkowski seems to have left FSL while ago)

   My goal here is to save as many 83xx based boards as possible
that I believe there are still new designs for and I have access to
their related eval boards.

   I just don't know if I should bug Kim each time or if
those mpc83xx board related patches could go through your
tree after sitting for comments in the m-l sometime. This
would make things a bit faster/simpler.

   Kim is cc'ed, perhaps he can chime in as well.

   Thanks

   Sinan Akman

>
> The merge window is now closed.  I'm going to do my best to keep to the
> every two weeks we do an RC thing again this time and continuing to rely
> on everyones best judgement about what level of changes they're going to
> put into a pull request to me.
>
> With -rc1 out, if things don't have a plan to move to generic board (for
> example I saw the series for microblaze) it's time to put up a removal
> series and CC anyone still listed as being interested in it.
>
> As always, if anything is broken please speak up.
>
> Thanks all!
>

  reply	other threads:[~2015-02-02 22:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 19:00 [U-Boot] [ANN] U-Boot v2015.04-rc1 released Tom Rini
2015-02-02 22:03 ` Sinan Akman [this message]
2015-02-02 22:14 ` Wolfgang Denk

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=54CFF44F.6020908@writeme.com \
    --to=sinan@writeme.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 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.