From: Alan Cox <alan@linux.intel.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Ds, Sreedhara" <sreedhara.ds@intel.com>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: Patch [4/4] intel scu ipc
Date: Fri, 28 May 2010 17:24:04 +0100 [thread overview]
Message-ID: <20100528172404.267674c3@linux.intel.com> (raw)
In-Reply-To: <20100528135059.GC25798@srcf.ucam.org>
On Fri, 28 May 2010 14:50:59 +0100
Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> On Fri, May 28, 2010 at 02:14:06PM +0530, Ds, Sreedhara wrote:
> > Subject: [PATCH] Remove indirect read write api support.
> > Firmware nolonger support these api, security issue
>
> What security issues?
It's just stuff that is gone, didn't work out internally. No driver
will use those methods, no public firmware will support them. Dead code
might be a better description.
It's not security in a Linux sense.
Alan
next prev parent reply other threads:[~2010-05-28 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 8:44 Patch [4/4] intel scu ipc Ds, Sreedhara
2010-05-28 13:50 ` Matthew Garrett
2010-05-28 16:24 ` Alan Cox [this message]
2010-05-30 15:44 ` Ds, Sreedhara
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=20100528172404.267674c3@linux.intel.com \
--to=alan@linux.intel.com \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sreedhara.ds@intel.com \
--cc=x86@kernel.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 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.