public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: lkml@pengaru.com, linux-kernel@vger.kernel.org,
	Wu Fengguang <fengguang.wu@intel.com>, miklos <miklos@szeredi.hu>
Subject: Re: bdi_min_ratio never shrinks, ultimately preventing valid setting of min_ratio
Date: Wed, 08 Jun 2011 12:45:48 +0200	[thread overview]
Message-ID: <1307529948.2322.322.camel@twins> (raw)
In-Reply-To: <1307525113.2322.291.camel@twins>

On Wed, 2011-06-08 at 11:25 +0200, Peter Zijlstra wrote:
> On Tue, 2011-06-07 at 17:13 -0700, Andrew Morton wrote:
> 
> > I grabbed this, wrote a changelog and stuck your signed-off-by on it. 
> 
> Thanks, I was still waiting for feedback :/
> 
> > I also added a cc:stable but I didn't work out how far back in time it
> > goes.  A long way, I think?
> 
> Yeah, ages ago:
> 
> commit 189d3c4a94ef19fca2a71a6a336e9fda900e25e7
> Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Date:   Wed Apr 30 00:54:35 2008 -0700
> 
>     mm: bdi: allow setting a minimum for the bdi dirty limit
> 
> git describe --contains doesn't seem to want to give a -linus release,
> my git foo is too weak :-(

OK after it was pointed out that --match takes a glob, not a regex, it
gives:

# git describe --contains  189d3c4a94ef19fca2a71a6a336e9fda900e25e7 --match 'v*'
v2.6.26-rc1~155

So yeah, _waaaay_ back.

      reply	other threads:[~2011-06-08 10:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01  0:28 bdi_min_ratio never shrinks, ultimately preventing valid setting of min_ratio lkml
2011-06-02 11:43 ` Peter Zijlstra
2011-06-02 18:32   ` lkml
2011-06-02 21:25     ` Peter Zijlstra
2011-06-08  0:13       ` Andrew Morton
2011-06-08  9:25         ` Peter Zijlstra
2011-06-08 10:45           ` Peter Zijlstra [this message]

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=1307529948.2322.322.camel@twins \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@pengaru.com \
    --cc=miklos@szeredi.hu \
    /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