From: Paolo Bonzini <pbonzini@redhat.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Gleb Natapov <gleb@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/3] Documentation/kvm: patches should be against linux.git
Date: Thu, 31 Oct 2013 11:59:27 +0100 [thread overview]
Message-ID: <5272380F.9000600@redhat.com> (raw)
In-Reply-To: <1383216396-12869-3-git-send-email-artagnon@gmail.com>
Il 31/10/2013 11:46, Ramkumar Ramachandra ha scritto:
> 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.
Maintainer have their repository at
git://git.kernel.org/pub/scm/virt/kvm/kvm.git. The right fix is to add
that tree to MAINTAINERS.
Paolo
> 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
>
parent reply other threads:[~2013-10-31 10:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1383216396-12869-3-git-send-email-artagnon@gmail.com>]
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=5272380F.9000600@redhat.com \
--to=pbonzini@redhat.com \
--cc=artagnon@gmail.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).