From: David Miller <davem@davemloft.net>
To: hch@lst.de
Cc: ak@suse.de, akpm@linux-foundation.org, ananth@in.ibm.com,
anil.s.keshavamurthy@intel.com, linux-arch@vger.kernel.org,
prasanna@in.ibm.com
Subject: Re: [patch 47/59] x86: optimize page faults like all other achitectures and kill notifier cruft
Date: Fri, 10 Aug 2007 16:59:13 -0700 (PDT) [thread overview]
Message-ID: <20070810.165913.58962051.davem@davemloft.net> (raw)
In-Reply-To: <20070810235207.GA28512@lst.de>
From: Christoph Hellwig <hch@lst.de>
Date: Sat, 11 Aug 2007 01:52:07 +0200
> I'm not going to let all this crappy and uneeded code rot in kprobes.c
> just because you disagree with everyone else.
FWIW I totally agree with Christoph on this.
prev parent reply other threads:[~2007-08-10 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 22:00 [patch 47/59] x86: optimize page faults like all other achitectures and kill notifier cruft akpm
2007-08-10 23:17 ` Andi Kleen
2007-08-10 23:52 ` Christoph Hellwig
2007-08-10 23:59 ` David Miller [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=20070810.165913.58962051.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--cc=prasanna@in.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 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).