From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: [PATCH 2/2] Fix NULL pointer dereference in ARINC653 free_vdata. Date: Mon, 4 Nov 2013 10:46:50 +0000 Message-ID: <52777B1A.4070300@eu.citrix.com> References: <1383252473-3067-1-git-send-email-nate.studer@dornerworks.com> <1383252473-3067-3-git-send-email-nate.studer@dornerworks.com> <5273B320.6070201@citrix.com> <5273B723.7090006@eu.citrix.com> <5276D5C7.8040100@dornerworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5276D5C7.8040100@dornerworks.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Nate Studer , Andrew Cooper Cc: robert.vanvossen@dornerworks.com, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 03/11/13 23:01, Nate Studer wrote: > On 11/1/2013 10:13 AM, George Dunlap wrote: >> Both these patches can have my Ack, BTW (although I don't think they >> need it): I just wanted to be a good citizen and do a bit of review. :-) > Thanks Andrew and George. > > Just to make sure, and to avoid needlessly filling George's inbox, Robbie (The > other ARINC653 scheduler maintainer) should usually be the one acking patches > like this, correct? Oh, don't worry about filling up my inbox. I do want to know what's going on in the scheduling area, and I probably *should* review this kind of patch anyway. I was just saying, I don't think the committers necessarily need to wait for an Ack from me to commit it. :-) I'm not sure exactly what the policy would be here -- I think the "need an ack from someone else" rule is primarily for committers to commit their own patches. If you're just submitting it, as a maintainer, it seems like having the committer look over it (and being satisfied that the community has had a chance to comment) should be enough, and needing an extra Ack from the other committer is a bit over-kill, particularly in this case. But I could be wrong about that. :-) -George