From: "Radim Krčmář" <rkrcmar@redhat.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: linux-mips@linux-mips.org, Paolo Bonzini <pbonzini@redhat.com>,
Ralf Baechle <ralf@linux-mips.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: MIPS: Add missing uaccess.h include
Date: Thu, 20 Oct 2016 19:53:23 +0200 [thread overview]
Message-ID: <20161020175323.GB8569@potion> (raw)
In-Reply-To: <20161020131630.GL7370@jhogan-linux.le.imgtec.org>
2016-10-20 14:16+0100, James Hogan:
> BTW, generally speaking do you always prefer pull requests to have the
> patches sent in reply to it, or only if they haven't already been posted
> for review?
I strongly prefer pull requests that include only patches that were
already posted on the list and slightly prefer to omit the patch
replies.
At least for me, a patch in a pull request has a FYI status instead of a
RFC status that a normal posting has.
[I'd like if all patches in pull requests were already (re)viewed by
interested parties, so merge discussions could be high level or focus
on things that we learned while/after applying the patches, hence there
would be little benefit from reposting patches to the mailing list.]
next prev parent reply other threads:[~2016-10-20 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 23:45 [PATCH] KVM: MIPS: Add missing uaccess.h include James Hogan
2016-10-20 13:10 ` Radim Krčmář
2016-10-20 13:16 ` James Hogan
2016-10-20 17:53 ` Radim Krčmář [this message]
2016-10-20 19:15 ` James Hogan
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=20161020175323.GB8569@potion \
--to=rkrcmar@redhat.com \
--cc=james.hogan@imgtec.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=pbonzini@redhat.com \
--cc=ralf@linux-mips.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