From: Andrew Morton <akpm@linux-foundation.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
npiggin@suse.de, hugh.dickins@tiscali.co.uk, avi@redhat.com,
torvalds@linux-foundation.org, aarcange@redhat.com
Subject: Re: [PATCH 0/2] ZERO PAGE again v4.
Date: Wed, 22 Jul 2009 17:47:41 -0700 [thread overview]
Message-ID: <20090722174741.79743e3a.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090723093334.3166e9d2.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, 23 Jul 2009 09:33:34 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> BTW, when I post new version, should I send a reply to old version to say
> "this version is obsolete" ? Can it make your work easier ? like following.
>
> Re:[PATCH][Obsolete] new version weill come (Was.....)
>
> I tend to update patches until v5 or more until merged.
Usually it's pretty clear when a new patch or patch series is going to
be sent. I think that simply resending it all is OK.
I don't pay much attention to the "version N" info either - it can be
unreliable and not everyone does it and chronological ordering works OK
for this.
Very occasionally I'll merge a patch and then discover a later version
further down through the backlog. But that's OK - I'll just update the
patch. Plus I'm not usually stuck this far in the past.
(I'm still trying to find half a day to read "Per-bdi writeback flusher
threads v12")
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-07-23 0:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 3:24 [PATCH 0/2] ZERO PAGE again v3 KAMEZAWA Hiroyuki
2009-07-09 3:27 ` [PATCH 1/2] ZERO PAGE config KAMEZAWA Hiroyuki
2009-07-09 3:28 ` [PATCH 2/2] ZERO PAGE by pte_special KAMEZAWA Hiroyuki
2009-07-09 3:58 ` Linus Torvalds
2009-07-09 4:54 ` KAMEZAWA Hiroyuki
2009-07-13 5:45 ` [PATCH 0/2] ZERO PAGE again v3 KAMEZAWA Hiroyuki
2009-07-16 9:01 ` [PATCH 0/2] ZERO PAGE again v4 KAMEZAWA Hiroyuki
2009-07-16 9:03 ` [PATCH 1/2] " KAMEZAWA Hiroyuki
2009-07-16 9:04 ` [PATCH 2/2] ZERO PAGE based on pte_special KAMEZAWA Hiroyuki
2009-07-16 12:00 ` Minchan Kim
2009-07-16 13:02 ` KAMEZAWA Hiroyuki
2009-07-17 0:38 ` KAMEZAWA Hiroyuki
2009-07-22 23:51 ` [PATCH 0/2] ZERO PAGE again v4 KAMEZAWA Hiroyuki
2009-07-23 0:12 ` Andrew Morton
2009-07-23 0:33 ` KAMEZAWA Hiroyuki
2009-07-23 0:47 ` Andrew Morton [this message]
2009-07-26 16:00 ` Hugh Dickins
2009-07-26 22:56 ` KAMEZAWA Hiroyuki
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=20090722174741.79743e3a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aarcange@redhat.com \
--cc=avi@redhat.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--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).