Re: [PATCH] arch/sparc: additional len check in loop for prom_getbootargs

[Chen Gang <gang.chen@asianux.com>]

Hi Julian Calaby:


thank you for your reply, firstly.

1) I think what you reply are valuable (at least, for me, it is true).

2) I have read Documents/SubmittingPatches (which Eric Dumazet suggested)

3) I also think, it will be better, if put part contents of your reply into Documents/SubmittingPatches as completion. 

thanks.

gchen.


于 2012年11月09日 13:06, Julian Calaby 写道:
> Hi Chen,
> 
> On Fri, Nov 9, 2012 at 2:15 PM, Chen Gang <gang.chen@asianux.com> wrote:
>> Hell David Miller:
>>
>> 1) Is this patch applied ?  or need some discussion ?  or suspended ?
>>
>> 2) If possible:
>>    A) can you tell me about our patch processing work flow "
>>    B) or some reference links (or document location) ?
> 
> In regards to patches, you should assume that maintainers are:
> 1. grumpy
> 2. overworked
> 3. looking at your patch as you email them about it.
> 
> (Note that only #2 is true, but it saves everyone time and aggravation
> if you assume the rest)
> 
> 11 hours is not long enough for David to get to your patch, review it
> and apply it. I don't believe that there are any maintainers which
> would get to a patch that quickly.
> 
> If David hadn't applied the patch within a few days of it being
> posted, then you might want to gently ask what's up. However, as Sam
> reviewed the patch and had some comments about it, it's unlikely that
> David will even look at it until you've addressed Sam's feedback.
> 
> The best way to get a patch into the kernel is to follow the rules in
> Documentation/SubmittingPatches which you have, respond quickly to any
> feedback, be patient, be prepared to explain why you're doing what
> you're doing, and be prepared to change and resubmit your patch many
> times until everyone is happy with it.
> 
> I'm sure that this is all written down in a document somewhere, but I
> can't recall what or where it is.
> 
> Thanks,
> 


-- 
Chen Gang

Asianux Corporation