From: Ben Hutchings <ben@decadent.org.uk>
To: paul.szabo@sydney.edu.au, 695182@bugs.debian.org
Cc: minchan@kernel.org, psz@maths.usyd.edu.au,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory
Date: Fri, 25 Jan 2013 13:01:53 +0000 [thread overview]
Message-ID: <1359118913.3146.3.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <201301250953.r0P9rOSe012192@como.maths.usyd.edu.au>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Fri, 2013-01-25 at 20:53 +1100, paul.szabo@sydney.edu.au wrote:
> Dear Minchan,
>
> > So what's the effect for user?
> > ...
> > It seems you saw old kernel.
> > ...
> > Current kernel includes ...
> > So I think we don't need this patch.
>
> As I understand now, my patch is "right" and needed for older kernels;
> for newer kernels, the issue has been fixed in equivalent ways; it was
> an oversight that the change was not backported; and any justification
> you need, you can get from those "later better" patches.
[...]
If you can identify where it was fixed then your patch for older
versions should go to stable with a reference to the upstream fix (see
Documentation/stable_kernel_rules.txt).
Ben.
--
Ben Hutchings
Q. Which is the greater problem in the world today, ignorance or apathy?
A. I don't know and I couldn't care less.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-01-25 22:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 9:53 paul.szabo
2013-01-25 13:01 ` Ben Hutchings [this message]
2013-01-25 23:49 ` Bug#695182: " paul.szabo
2013-01-26 0:10 ` Ben Hutchings
2013-01-26 3:05 ` paul.szabo
2013-01-26 3:07 ` paul.szabo
2013-01-26 3:17 ` Ben Hutchings
2013-01-26 0:14 ` Jonathan Nieder
2013-01-26 15:43 ` Theodore Ts'o
2013-01-26 7:44 ` Bug#695182: " Jonathan Nieder
2013-01-26 20:23 ` paul.szabo
2013-01-28 6:23 ` Minchan Kim
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=1359118913.3146.3.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=695182@bugs.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=paul.szabo@sydney.edu.au \
--cc=psz@maths.usyd.edu.au \
/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