From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Release status - things to be done
Date: Sun, 06 Jul 2008 00:17:10 -0700 [thread overview]
Message-ID: <48707176.4020000@gmail.com> (raw)
In-Reply-To: <20080705230540.22A8C248AC@gemini.denx.de>
Hi Wolfgang,
Wolfgang Denk wrote:
> Hi everybody,
>
> here is a summary of the current state of my processing of patches
> that have been submitted for the upcoming 1.3.4 release.
>
> As you might have noticed, I've been on vacation for the last two
> weeks, and I spent this time (intentionally) completely offline. So
> please apologize if parts of the following comments / questions have
> been obsoleted by recent events - I will try to catch up as soon as
> possible, but I think it is better to send out this summary now,
> i. e. _before_ I start reading he backlog of the last two weeks.
>
>
> Here is a list of patches I had marked as open in my list, with
> comments about their state, including comments who I consider to be
> responsible for further progress:
>
>
<snip>
> 3645 06/11 Nobuhiro Iwamatsu [U-Boot-Users] [PATCH v2] net: sh: Renesas SH7763 Ethernet device support
> -> for net custodian
>
>
Didn't pick this up because it was after what I thought was the cut-off
of 6/10. It still has issues, so I'll ask NobuHiro to re-submit.
Should it go in this release when OK?
<snip>
> 3812 06/13 Ben Warren [PATCH V4] Add mechanisms for CPU and board-specific Ethernet initialization
> -> for net custodian.
>
>
Again, thought it was too late. I'll send a pull request soon that will
include this one.
<snip>
> 3901 06/17 Nobuhiro Iwamatsu [U-Boot-Users] [PATCH] net: ne2000: Move dev_addr variable from grobal to local.
> 3902 06/17 Nobuhiro Iwamatsu [U-Boot-Users] [PATCH] net: ne2000: Fix compile error of NE2000
> -> for net custodian
>
>
These are good ones, and will be in my pull request. Same deal with the
date.
<snip>
> 3984 06/18 Hugo Villeneuve [U-Boot-Users] [PATCH 1/2] Remove duplicate definitions in include/lxt971a.h.
> 3985 06/18 Hugo Villeneuve [U-Boot-Users] [PATCH 2/2] Remove duplicate code in cpu/arm926ejs/davinci/lxt972.c.
> -> for net custodian
>
>
Missed these completely, since no clues in title about networking...
regards,
Ben
next prev parent reply other threads:[~2008-07-06 7:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 23:05 [U-Boot-Users] Release status - things to be done Wolfgang Denk
2008-07-06 5:24 ` Shinya Kuribayashi
2008-07-06 7:17 ` Ben Warren [this message]
2008-07-06 7:54 ` Wolfgang Denk
2008-07-07 2:54 ` Nobuhiro Iwamatsu
2008-07-07 6:13 ` Ben Warren
2008-07-06 9:00 ` Magnus Lilja
2008-07-06 10:51 ` Jean-Christophe PLAGNIOL-VILLARD
2008-07-06 11:28 ` Nobuhiro Iwamatsu
2008-07-07 9:05 ` Stefan Roese
2008-07-07 9:37 ` Wolfgang Denk
2008-07-07 9:50 ` Stefan Roese
2008-07-07 10:21 ` Stefan Roese
2008-07-07 18:18 ` Scott Wood
2008-07-07 14:28 ` John Rigby
2008-07-07 15:03 ` Wolfgang Denk
2008-07-07 14:32 ` Scott Wood
2008-07-07 18:23 ` Jon Loeliger
2008-07-07 18:55 ` Kim Phillips
2008-07-07 20:30 ` Rune Torgersen
2008-07-07 20:41 ` Rune Torgersen
2008-07-09 23:34 ` Anatolij Gustschin
2008-07-10 11:12 ` Haavard Skinnemoen
-- strict thread matches above, loose matches on Subject: below --
2008-07-09 19:46 Liew Tsi Chung
2008-07-09 21:02 ` 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=48707176.4020000@gmail.com \
--to=biggerbadderben@gmail.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