From: Dan Rosenberg <drosenberg@vsecurity.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Urs Thuermann <urs.thuermann@volkswagen.de>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, security@kernel.org
Subject: Re: [PATCH] CAN: Use inode instead of kernel address for /proc file
Date: Sun, 26 Dec 2010 11:38:43 -0500 [thread overview]
Message-ID: <1293381523.9764.52.camel@Dan> (raw)
In-Reply-To: <4D17270B.5000204@hartkopp.net>
On Sun, 2010-12-26 at 12:29 +0100, Oliver Hartkopp wrote:
> Convinced? 8-)
>
Absolutely. I didn't mean to come across as argumentative, I was just
trying to anticipate potential objections. I'll resend shortly.
Thanks,
Dan
prev parent reply other threads:[~2010-12-26 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-25 22:16 [PATCH] CAN: Use inode instead of kernel address for /proc file Dan Rosenberg
2010-12-25 22:22 ` Oliver Hartkopp
2010-12-25 22:31 ` Oliver Hartkopp
2010-12-25 22:41 ` Dan Rosenberg
2010-12-26 11:29 ` Oliver Hartkopp
2010-12-26 16:38 ` Dan Rosenberg [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=1293381523.9764.52.camel@Dan \
--to=drosenberg@vsecurity.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=security@kernel.org \
--cc=socketcan@hartkopp.net \
--cc=urs.thuermann@volkswagen.de \
/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).