From: Christoph Hellwig <hch@infradead.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, Denys Vlasenko <dvlasenk@redhat.com>,
Hugh Dickins <hughd@google.com>,
Jim Keniston <jkenisto@us.ibm.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] uprobes: tmpfs support
Date: Mon, 2 Jun 2014 11:30:28 -0700 [thread overview]
Message-ID: <20140602183028.GA9372@infradead.org> (raw)
In-Reply-To: <20140602141406.GA17863@redhat.com>
On Mon, Jun 02, 2014 at 04:14:06PM +0200, Oleg Nesterov wrote:
> Ingo, please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/oleg/misc uprobes/core
>
> Based on tip:perf/uprobes
Eww, adding tmpfs-specific code to uprobes screams layering violation.
Hugh, what is the problem with implementing ->readpage for tmpfs again?
next prev parent reply other threads:[~2014-06-02 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 14:14 [GIT PULL] uprobes: tmpfs support Oleg Nesterov
2014-06-02 18:30 ` Christoph Hellwig [this message]
2014-06-02 19:09 ` Hugh Dickins
2014-06-02 19:23 ` Oleg Nesterov
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=20140602183028.GA9372@infradead.org \
--to=hch@infradead.org \
--cc=dvlasenk@redhat.com \
--cc=hughd@google.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=srikar@linux.vnet.ibm.com \
/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.