linux-kernel - Re: [PATCH 0/2] ZERO PAGE again v4.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 22 Jul 2009 17:47:41 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org, npiggin@...e.de,
	hugh.dickins@...cali.co.uk, avi@...hat.com,
	torvalds@...ux-foundation.org, aarcange@...hat.com
Subject: Re: [PATCH 0/2] ZERO PAGE again v4.

On Thu, 23 Jul 2009 09:33:34 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/