From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] patches never reviewed
Date: Tue, 4 Jun 2013 12:54:31 -0500 [thread overview]
Message-ID: <1370368471.748.7@snotra> (raw)
In-Reply-To: <1370368067.748.6@snotra> (from scottwood@freescale.com on Tue Jun 4 12:47:47 2013)
On 06/04/2013 12:47:47 PM, Scott Wood wrote:
> On 06/03/2013 03:51:48 PM, Angelo Dureghello wrote:
>> Dear All,
>>
>> i worked hardly through v6 for approval of this AMCORE Coldfire
>> board support.
>>
>> Waited patiently for review of this patches:
>>
>> http://patchwork.ozlabs.org/patch/215904/
>> http://patchwork.ozlabs.org/patch/214686/
>>
>> then asked again later for the review:
>>
>> http://marc.info/?l=u-boot&m=136059580219228&w=2
>>
>> still, at today, i had no feedbacks.
>>
>> Unfortunately (i can be wrong) but i have the impression at freescale
>> no-one have time to spend for following this board addition.
>
> Jason Jin is the Coldfire custodian. I've added him on CC here;
> please be sure to put him on CC when you send Coldfire patches or
> inquiries.
Sigh, and of course the list ate the CC. So for all I know maybe you
had him on CC to begin with...
Another thing that can help is using better subject lines. "patches
review" isn't going to let people know what sort of patches they are
and if it's their responsibility or not. Likewise, "board: add support
for amcore board" doesn't have m68k or coldfire in the title (whereas
"board:" is redundant).
-Scott
next prev parent reply other threads:[~2013-06-04 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 20:51 [U-Boot] patches never reviewed Angelo Dureghello
2013-06-04 17:47 ` Scott Wood
2013-06-04 17:54 ` Scott Wood [this message]
2013-06-06 14:20 ` Angelo Dureghello
2013-06-06 14:39 ` Otavio Salvador
2013-06-07 5:55 ` Jin Zhengxiong-R64188
2013-06-05 3:21 ` Jin Zhengxiong-R64188
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=1370368471.748.7@snotra \
--to=scottwood@freescale.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