From: Ramkumar Ramachandra <artagnon@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Gleb Natapov <gleb@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, Avi Kivity <avi@redhat.com>
Subject: [PATCH 2/3] Documentation/kvm: patches should be against linux.git
Date: Thu, 31 Oct 2013 16:16:35 +0530 [thread overview]
Message-ID: <1383216396-12869-3-git-send-email-artagnon@gmail.com> (raw)
In-Reply-To: <1383216396-12869-1-git-send-email-artagnon@gmail.com>
The document hasn't been updated since cf3e3d3 (KVM: Document KVM
specific review items, 2010-06-24); kvm does not have a separate
repository anymore.
Cc: Avi Kivity <avi@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
---
Documentation/virtual/kvm/review-checklist.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/virtual/kvm/review-checklist.txt b/Documentation/virtual/kvm/review-checklist.txt
index a850986..8385c4d 100644
--- a/Documentation/virtual/kvm/review-checklist.txt
+++ b/Documentation/virtual/kvm/review-checklist.txt
@@ -4,7 +4,7 @@ Review checklist for kvm patches
1. The patch must follow Documentation/CodingStyle and
Documentation/SubmittingPatches.
-2. Patches should be against kvm.git master branch.
+2. Patches should be against linux.git master branch.
3. If the patch introduces or modifies a new userspace API:
- the API must be documented in Documentation/virtual/kvm/api.txt
--
1.8.5.rc0
next prev parent reply other threads:[~2013-10-31 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 10:46 [PATCH 0/3] Small patches around kvm doc Ramkumar Ramachandra
2013-10-31 10:46 ` [PATCH 1/3] MAINTAINERS: fix broken link to www.linux-kvm.org Ramkumar Ramachandra
2013-10-31 10:46 ` Ramkumar Ramachandra [this message]
2013-10-31 10:59 ` [PATCH 2/3] Documentation/kvm: patches should be against linux.git Paolo Bonzini
2013-10-31 10:46 ` [PATCH 3/3] Documentation/kvm: add a 00-INDEX file Ramkumar Ramachandra
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=1383216396-12869-3-git-send-email-artagnon@gmail.com \
--to=artagnon@gmail.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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).