From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Valdis.Kletnieks@vt.edu, akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Nitin Gupta <ngupta@vflare.org>
Subject: RE: mmotm 2011-02-10-16-26 uploaded
Date: Fri, 11 Feb 2011 14:09:03 -0800 (PST) [thread overview]
Message-ID: <b4feb995-1e73-4c12-8c58-ad0c2252233c@default> (raw)
In-Reply-To: <53491.1297461155@localhost>
> From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
> Sent: Friday, February 11, 2011 2:53 PM
> To: akpm@linux-foundation.org; Dan Magenheimer
> Cc: mm-commits@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
> mm@kvack.org; linux-fsdevel@vger.kernel.org
> Subject: Re: mmotm 2011-02-10-16-26 uploaded
>
> On Thu, 10 Feb 2011 16:26:36 PST, akpm@linux-foundation.org said:
> > The mm-of-the-moment snapshot 2011-02-10-16-26 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
>
> CONFIG_ZCACHE=m dies a horrid death:
Thanks Valdis. A fix for this has already been posted by
Nitin Gupta and Randy Dunlap here:
https://lkml.org/lkml/2011/2/10/383
Another patch for a zcache memory leak has been posted here:
https://lkml.org/lkml/2011/2/10/306
I'm sorry that multiple people have run into this in
multiple trees.
I have to admit I am a bit baffled as to what the proper
tree flow is for bug fixes like this, but would be happy
to "follow the process" if I am told what it is or if
someone can point me to a document describing it.
(Clearly making sure there are no bugs at all in a
submission is the best way to go, but I'm afraid
I can't claim to be perfect :-)
Thanks,
Dan
P.S. I suppose there isn't really a good reason for
CONFIG_ZCACHE to be tri-state as it really makes
no sense as a module because, if CONFIG_CLEANCACHE
is enabled, it will always get loaded.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-02-11 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 0:26 mmotm 2011-02-10-16-26 uploaded akpm
2011-02-11 21:52 ` Valdis.Kletnieks
2011-02-11 22:09 ` Dan Magenheimer [this message]
2011-02-12 2:47 ` mmotm 2011-02-10-16-26 uploaded (zcache') Randy Dunlap
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=b4feb995-1e73-4c12-8c58-ad0c2252233c@default \
--to=dan.magenheimer@oracle.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=ngupta@vflare.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).