public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@minantech.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: Andrew Morton <akpm@osdl.org>,
	nickpiggin@yahoo.com.au, mst@mellanox.co.il, hugh@veritas.com,
	wli@holomorphy.com, benh@kernel.crashing.org,
	linux-kernel@vger.kernel.org, openib-general@openib.org,
	vandrove@vc.cvut.cz, pbadari@us.ibm.com,
	grundler@parisc-linux.org, matthew@wil.cx
Subject: Re: [PATCH] Fix up MADV_DONTFORK/MADV_DOFORK definitions
Date: Wed, 15 Feb 2006 08:48:36 +0200	[thread overview]
Message-ID: <20060215064836.GG24524@minantech.com> (raw)
In-Reply-To: <adaslqlqgdz.fsf_-_@cisco.com>

On Tue, Feb 14, 2006 at 10:34:48PM -0800, Roland Dreier wrote:
>     Andrew> yes, please do.
> 
> OK, here's a patch that changes them to 9 and 10.  I would hold off
> sending this to Linus until Michael has a chance to speak up, in case
> there's a reason I don't know for choosing 0x30 and 0x31.
> 
Here
http://marc.theaimsgroup.com/?l=linux-kernel&m=113162971606408&w=2
at the end there is a reasoning. So I think 9 and 10 will do too.
By the way Nick was on CC list back than and haven't raised any 
concerns :)


--
			Gleb.

  reply	other threads:[~2006-02-15  6:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 15:41 madvise MADV_DONTFORK/MADV_DOFORK Michael S. Tsirkin
2006-02-13 18:23 ` Hugh Dickins
2006-02-13 19:02   ` Michael S. Tsirkin
2006-02-14  6:51     ` Gleb Natapov
2006-02-13 19:04 ` [openib-general] " Roland Dreier
2006-02-13 19:05 ` Linus Torvalds
2006-02-13 19:16   ` [openib-general] " Roland Dreier
2006-02-13 19:34     ` Linus Torvalds
2006-02-13 19:50       ` Hugh Dickins
2006-02-13 21:09         ` Michael S. Tsirkin
2006-02-13 21:57           ` Hugh Dickins
2006-02-13 22:09             ` Michael S. Tsirkin
2006-02-13 22:54               ` Hugh Dickins
2006-02-13 23:01                 ` [PATCH] " Michael S. Tsirkin
2006-02-13 23:44                   ` Hugh Dickins
2006-02-13 22:27             ` [openib-general] " Linus Torvalds
2006-02-13 22:55               ` Michael S. Tsirkin
2006-02-13 23:01                 ` Hugh Dickins
2006-02-13 23:35                   ` [PATCH] " Michael S. Tsirkin
2006-02-15  4:31                     ` Nick Piggin
2006-02-15  6:09                       ` Roland Dreier
2006-02-15  6:16                         ` Andrew Morton
2006-02-15  6:34                           ` [PATCH] Fix up MADV_DONTFORK/MADV_DOFORK definitions Roland Dreier
2006-02-15  6:48                             ` Gleb Natapov [this message]
2006-02-15  7:06                               ` Nick Piggin
2006-02-15  7:31                             ` Bernd Eckenfels
2006-02-15  8:18                             ` Michael S. Tsirkin
2006-02-15  8:13                         ` [PATCH] madvise MADV_DONTFORK/MADV_DOFORK Michael S. Tsirkin
2006-02-13 20:05       ` Michael S. Tsirkin
2006-02-13 19:20   ` Michael S. Tsirkin

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=20060215064836.GG24524@minantech.com \
    --to=gleb@minantech.com \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=grundler@parisc-linux.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mst@mellanox.co.il \
    --cc=nickpiggin@yahoo.com.au \
    --cc=openib-general@openib.org \
    --cc=pbadari@us.ibm.com \
    --cc=rdreier@cisco.com \
    --cc=vandrove@vc.cvut.cz \
    --cc=wli@holomorphy.com \
    /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