xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Nate Studer <nate.studer@dornerworks.com>
To: George Dunlap <george.dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Cc: robert.vanvossen@dornerworks.com, xen-devel@lists.xen.org
Subject: Re: [PATCH 2/2] Fix NULL pointer dereference in ARINC653 free_vdata.
Date: Sun, 3 Nov 2013 18:01:27 -0500	[thread overview]
Message-ID: <5276D5C7.8040100@dornerworks.com> (raw)
In-Reply-To: <5273B723.7090006@eu.citrix.com>

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?

> 
>   -George
> 

  parent reply	other threads:[~2013-11-03 23:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 20:47 [PATCH 0/2] Fix crashes with arinc653 cpupools Nathan Studer
2013-10-31 20:47 ` [PATCH 1/2] Fix sched_priv corruption in ARINC653 alloc_vdata Nathan Studer
2013-11-01 13:53   ` Andrew Cooper
2013-11-03 23:07     ` Nate Studer
2013-11-04 15:49   ` George Dunlap
2013-10-31 20:47 ` [PATCH 2/2] Fix NULL pointer dereference in ARINC653 free_vdata Nathan Studer
2013-11-01 13:56   ` Andrew Cooper
2013-11-01 14:13     ` George Dunlap
2013-11-01 14:17       ` Andrew Cooper
2013-11-03 23:01       ` Nate Studer [this message]
2013-11-04 10:46         ` George Dunlap
2013-11-04 10:55           ` Ian Campbell
2013-11-04 15:15           ` Jan Beulich

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=5276D5C7.8040100@dornerworks.com \
    --to=nate.studer@dornerworks.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=robert.vanvossen@dornerworks.com \
    --cc=xen-devel@lists.xen.org \
    /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).