From: Thomas Chou <thomas@wytron.com.tw>
To: u-boot@lists.denx.de
Subject: [U-Boot] nios2 custodian
Date: Wed, 26 May 2010 09:00:08 +0800 [thread overview]
Message-ID: <4BFC7298.9090502@wytron.com.tw> (raw)
In-Reply-To: <20100525112249.786AFE22AD1@gemini.denx.de>
Wolfgang Denk wrote:
> Thanks for your offer. I understand you are concerned that your
> patches don't get processed as fast as you'd like. I'm sorry for
> that.
Yes. This is my sole concern. Though we are all very busy, it is
importance to have timely response to the community.
> So far, Scott has done a good job as custodian. As far as I remember,
> there have never been any complaints about his work. Also, he assured
> me that he is willing to continue performing this duty, to the best of
> his capabilities.
Yes, I agree. Scott did a good job. Please keep on.
>>From the point of quality assurance it is always a good thing to have
> somebody else but the original author doing the final checking of the
> code.
Yes, it is good.
I think a custodian should also response early to patches with global
changes like that of arch dir move and root Makefile cleanup.
> I would therefore like to continue working as we do now, with Scott as
> custodian, at least for the time being. And I will try to keep an eye
> on the state of affairs for the NIOS patches.
I have two more mmc patches waiting for Andy's review,
05/03 [PATCH 1/3] lib: add crc7 from Linux
05/19 [PATCH 3/3 v8] mmc: add generic mmc spi driver
Once they get merged, I will update the nios wiki to use u-boot mainline
instead of our local branch. Beside, we are going to add fdt to nios2
linux, we will need your grand support.
Thank you very much for your attention. Thanks to Scott, too.
Best regards,
Thomas
prev parent reply other threads:[~2010-05-26 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 6:34 [U-Boot] nios2 custodian Thomas Chou
2010-05-25 11:22 ` Wolfgang Denk
2010-05-26 1:00 ` Thomas Chou [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=4BFC7298.9090502@wytron.com.tw \
--to=thomas@wytron.com.tw \
--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