From: Ian Campbell <ian.campbell@citrix.com>
To: Marcin Cieslak <saper@saper.info>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [PATCH 1/4] Use proper header guard for <ufs/ufs.h>
Date: Tue, 16 Sep 2014 17:23:12 +0100 [thread overview]
Message-ID: <1410884592.23505.3.camel@citrix.com> (raw)
In-Reply-To: <1410642625-45876-1-git-send-email-saper@saper.info>
On Sat, 2014-09-13 at 21:10 +0000, Marcin Cieslak wrote:
I didn't spot this on the first patch I commented on but all patches
accepted into Xen need to have a Signed-off-by. Please see
http://wiki.xen.org/wiki/Submitting_Xen_Patches#Signing_off_a_patch.
Ian.
next prev parent reply other threads:[~2014-09-16 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 21:10 [PATCH 1/4] Use proper header guard for <ufs/ufs.h> Marcin Cieslak
2014-09-13 21:10 ` [PATCH 2/4] libxl_get_scheduler() cannot return ERROR_FAIL Marcin Cieslak
2014-09-16 16:27 ` Ian Campbell
2014-09-13 21:10 ` [PATCH 3/4] libxl: shutdown_reason cannot be unsigned Marcin Cieslak
2014-09-16 18:43 ` Julien Grall
2014-09-13 21:10 ` [PATCH 4/4] libxl: Use yajl_gen_status_ok where appropriate Marcin Cieslak
2014-09-16 16:29 ` Ian Campbell
2014-09-16 16:23 ` Ian Campbell [this message]
2014-09-16 16:28 ` [PATCH 1/4] Use proper header guard for <ufs/ufs.h> Ian Campbell
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=1410884592.23505.3.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=saper@saper.info \
--cc=xen-devel@lists.xenproject.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).