linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: linux-mm@kvack.org, Nitin Gupta <ngupta@vflare.org>,
	Konrad Wilk <konrad.wilk@oracle.com>,
	Sasha Levin <levinsasha928@gmail.com>
Subject: Re: help converting zcache from sysfs to debugfs?
Date: Wed, 20 Jun 2012 10:40:59 -0500	[thread overview]
Message-ID: <4FE1EF0B.2050109@linux.vnet.ibm.com> (raw)
In-Reply-To: <83884ff2-1a06-4d9c-a7eb-c53ab0cbb6b1@default>

On 06/20/2012 10:30 AM, Dan Magenheimer wrote:

> But forgive me if I nearly have a heart attack as I
> contemplate another chicken-and-egg scenario trying
> to get debugfs-support-for-atomics upstream before
> zcache code that depends on it.


I don't think this is the same situation as most of our
other chicken and egg situations.  This is a very generic
addition to debugfs (i.e. someone anyone can use, not just
zcache).  Especially as more people use debugfs or convert
some of their sysfs to debufs. In all honesty, I'm surprised
it hasn't been added sooner.

--
Seth

--
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:[~2012-06-20 15:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20  0:29 help converting zcache from sysfs to debugfs? Dan Magenheimer
2012-06-20 11:03 ` Konrad Rzeszutek Wilk
2012-06-20 15:24   ` Dan Magenheimer
2012-06-20 14:20 ` Seth Jennings
2012-06-20 14:36 ` Seth Jennings
2012-06-20 15:30   ` Dan Magenheimer
2012-06-20 15:40     ` Seth Jennings [this message]
2012-06-20 16:56     ` Konrad Rzeszutek Wilk

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=4FE1EF0B.2050109@linux.vnet.ibm.com \
    --to=sjenning@linux.vnet.ibm.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=levinsasha928@gmail.com \
    --cc=linux-mm@kvack.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).