From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] UEC/NET patch status?
Date: Mon, 30 Aug 2010 14:36:17 -0700 [thread overview]
Message-ID: <4C7C2451.40708@gmail.com> (raw)
In-Reply-To: <OF86738C36.7ABEAAD2-ONC125778F.00744751-C125778F.00756932@transmode.se>
On 8/30/2010 2:22 PM, Joakim Tjernlund wrote:
> some time ago I submitted:
>
> [PATCH 1/2] UEC: Don't udelay needlessly
> [PATCH 2/2] UEC PHY: Remove strange 0.5 sec delay
> [PATCHv2] net: Fix faulty definition of uec_initialize()
> [PATCH] UEC PHY: Speed up initial PHY neg.
>
> The two first got an Ack from Kim, but the other two
> has not. None of them have showed up the the u-boot repo.
> I have tried to get some feedback(read prodding) but
> no such luck. The NET part in u-boot is moving really slow
> and I suspect my patches are already forgotten?
>
No, not forgotten, just in a queue. I'm acutely aware that this is
moving slowly, and will pull yours and other peoples stuff in *soon*.
Sorry, but other things that do have open merge windows have gotten
priority lately.
> Jocke
>
regards,
Ben
prev parent reply other threads:[~2010-08-30 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 21:22 [U-Boot] UEC/NET patch status? Joakim Tjernlund
2010-08-30 21:36 ` Ben Warren [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=4C7C2451.40708@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