From: Andrew Morton <akpm@linux-foundation.org>
To: Gleb Natapov <gleb@redhat.com>
Cc: avi@redhat.com, mtosatti@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Rik van Riel <riel@redhat.com>, Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH 1/2] Allow GUP to fail instead of waiting on a page.
Date: Wed, 2 Feb 2011 11:37:50 -0800 [thread overview]
Message-ID: <20110202113750.367a6fda.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110202133157.GI14984@redhat.com>
On Wed, 2 Feb 2011 15:31:57 +0200
Gleb Natapov <gleb@redhat.com> wrote:
> > This?
> >
> Yes, this is better. Thanks you. I see that the patch below is in your queue
> already. Should I re-spin my patch with improved comment anyway?
Nope, that's OK - I fold fixup patches into the base patch before
sending them onwards.
There's always a risk that someone will get a hold of an earlier
version of the patch, but a) sending out a v2 doesn't eliminate that
risk and b) it's not very important anyway (in this case) and c)
because I separate the base patch from the fixup patches, I'll easily
notice if someone merges an earlier patch, because I'm left holding
stray fixup patches.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-02-02 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 11:21 [PATCH 0/2] KVM: enable asynchronous page faults Gleb Natapov
2011-02-01 11:21 ` [PATCH 1/2] Allow GUP to fail instead of waiting on a page Gleb Natapov
2011-02-01 16:48 ` Rik van Riel
2011-02-02 0:42 ` Andrew Morton
2011-02-02 13:31 ` Gleb Natapov
2011-02-02 19:37 ` Andrew Morton [this message]
2011-02-01 11:21 ` [PATCH 2/2] KVM: Enable async page fault processing Gleb Natapov
2011-02-22 8:38 ` Lai Jiangshan
2011-03-24 12:22 ` Gleb Natapov
2011-03-24 13:23 ` Avi Kivity
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=20110202113750.367a6fda.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtosatti@redhat.com \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.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).