All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Herbert van den Bergh <herbert.van.den.bergh@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Dave McCracken <dave.mccracken@oracle.com>,
	Chris Mason <chris.mason@oracle.com>
Subject: Re: [PATCH] do not limit locked memory when RLIMIT_MEMLOCK is RLIM_INFINITY
Date: Fri, 13 Jul 2007 10:31:32 -0700	[thread overview]
Message-ID: <20070713103132.38e782e5.akpm@linux-foundation.org> (raw)
In-Reply-To: <46979C4E.6000205@oracle.com>

On Fri, 13 Jul 2007 08:37:50 -0700 Herbert van den Bergh <herbert.van.den.bergh@oracle.com> wrote:

> Andrew Morton wrote:
> > 
> > OK.  Seems like a nasty bug if one happens to want to do that.  Should we
> > backport this into 2.6.22.x?
> > 
> 
> Yes, please.  Do you need me to do anything for that?
> 

Nope.  I stick a "Cc: <stable@kernel.org>" into the changelog and then
magic happens: the -stable maintainers get a copy of the patch when it goes
to Linus, they get notification when I drop it after Linus merged it and
then they (hopeully) take the patch from Linus's tree.

(But the last step is a bit of a hassle - I suspect they take my emailed
version instead, but it would be super-rare for that to differ from the
version which Linus merged)

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Herbert van den Bergh <herbert.van.den.bergh@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Dave McCracken <dave.mccracken@oracle.com>,
	Chris Mason <chris.mason@oracle.com>
Subject: Re: [PATCH] do not limit locked memory when RLIMIT_MEMLOCK is RLIM_INFINITY
Date: Fri, 13 Jul 2007 10:31:32 -0700	[thread overview]
Message-ID: <20070713103132.38e782e5.akpm@linux-foundation.org> (raw)
In-Reply-To: <46979C4E.6000205@oracle.com>

On Fri, 13 Jul 2007 08:37:50 -0700 Herbert van den Bergh <herbert.van.den.bergh@oracle.com> wrote:

> Andrew Morton wrote:
> > 
> > OK.  Seems like a nasty bug if one happens to want to do that.  Should we
> > backport this into 2.6.22.x?
> > 
> 
> Yes, please.  Do you need me to do anything for that?
> 

Nope.  I stick a "Cc: <stable@kernel.org>" into the changelog and then
magic happens: the -stable maintainers get a copy of the patch when it goes
to Linus, they get notification when I drop it after Linus merged it and
then they (hopeully) take the patch from Linus's tree.

(But the last step is a bit of a hassle - I suspect they take my emailed
version instead, but it would be super-rare for that to differ from the
version which Linus merged)

--
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>

  reply	other threads:[~2007-07-13 17:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10  0:59 [PATCH] do not limit locked memory when RLIMIT_MEMLOCK is RLIM_INFINITY Herbert van den Bergh
2007-07-10  0:59 ` Herbert van den Bergh
2007-07-13  7:44 ` Andrew Morton
2007-07-13  7:44   ` Andrew Morton
2007-07-13 15:37   ` Herbert van den Bergh
2007-07-13 15:37     ` Herbert van den Bergh
2007-07-13 17:31     ` Andrew Morton [this message]
2007-07-13 17:31       ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2007-07-10  0:26 Herbert van den Bergh
2007-07-10  0:26 ` Herbert van den Bergh
2007-07-10  0:41 ` KAMEZAWA Hiroyuki
2007-07-10  0:41   ` KAMEZAWA Hiroyuki
2007-07-10  0:47 ` Randy Dunlap
2007-07-10  0:47   ` Randy Dunlap
2007-06-28 18:25 Herbert van den Bergh

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=20070713103132.38e782e5.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=dave.mccracken@oracle.com \
    --cc=herbert.van.den.bergh@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.