From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Tirumala Reddy Marri <tmarri@amcc.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: patch status
Date: Mon, 7 Dec 2009 19:52:57 -0500 [thread overview]
Message-ID: <20091208005257.GL2937@zod.rchland.ibm.com> (raw)
In-Reply-To: <AC5E1C3367E37D44970B81A6ADD1DA2C0872CE8B@SDCEXCHANGE01.ad.amcc.com>
On Mon, Dec 07, 2009 at 02:01:58PM -0800, Tirumala Reddy Marri wrote:
>Hi Ben,
>
> Did you get the chance to review the patch I sent it on Dec-1 2009
>
>
>
>http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-December/078436.html
Ben has to review lots of patches. Please be patient. Also, your patch is
tracked via patchwork here:
http://patchwork.ozlabs.org/patch/39865/
so you can see the state as it progresses.
Further, it would have been helpful to CC the maintainer of the 4xx sub-arch
(me) since it impacts that platform and you could have gotten some review more
quickly. I didn't notice it until this afternoon.
Lastly, your patch has lots of magical values in it. While I have no doubt
they are correct, I can't find any documentation for 460SX on the AMCC website
aside from some small product briefs. Perhaps I've overlooked the CPU manual,
but since I don't have such a board or the manual for it, it would be nice to
know what kind of testing has been done with this patch. A simple statement
such as "tested on kernel <version> with a <network, raid, whatever> pci-e
card successfully" would go a long way.
This is not a rant or complaint about the code. Just a reminder that the
community doesn't always move at the pace we would all like :). I'll try and
look over the patch more carefully tomorrow.
josh
next prev parent reply other threads:[~2009-12-08 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 22:01 patch status Tirumala Reddy Marri
2009-12-08 0:52 ` Josh Boyer [this message]
2009-12-08 1:41 ` Tirumala Reddy Marri
2009-12-08 2:59 ` Josh Boyer
2009-12-08 16:53 ` Tirumala Reddy Marri
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=20091208005257.GL2937@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tmarri@amcc.com \
/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;
as well as URLs for NNTP newsgroup(s).