From: Greg KH <greg@kroah.com>
To: Mark Allyn <mark.a.allyn@intel.com>
Cc: linux-kernel@vger.kernel.org, alan@linux.intel.com,
charles.f.johnson@intel.com
Subject: Re: [PATCH] Changes to integrate RAR with SEP and fix RAR problems
Date: Tue, 6 Oct 2009 14:29:36 -0700 [thread overview]
Message-ID: <20091006212936.GA21996@kroah.com> (raw)
In-Reply-To: <1254861953-18099-1-git-send-email-mark.a.allyn@intel.com>
On Tue, Oct 06, 2009 at 01:45:53PM -0700, Mark Allyn wrote:
> SEP stands for Security Processor; a dedicated processor
> that does encryption, decryption, key management, and
> secure storage.
>
> RAR stands for Restricted Access Region; this is memory
> aboard the MID platform that is restricted (via hardware)
> from access by software running on the x86 processor.
> Dedicated 'smart' peripherals such as sound, video, and
> encryption can access these regions of memory. They are here
> to help protect copyrighted midia from being illegally copied.
How does it allow "fair-use" copying? To prevent that is considered
illegal in some juristictions :)
> This is upstream revision 4 of the RAR driver.
>
> This is a patch referenced from the linux-next repository
> as pulled on October 6, 2009; from the following URL:
Why are you deleting the existing driver entirely? Why not just patch
it to have whatever new things you need here?
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
>
> This is a modified RAR driver to include integration with
> the SEP driver
>
> Plese be aware that the SEP driver requires this driver
> in order to compile and run. There are API function calls
> within this driver that are required by the SEP driver.
>
> Other drivers being developed in the future will also
> require this driver.
What drivers? In what way will it be required?
Your patch contains a number of obvious problems that
scripts/checkpatch.pl would have caught. Please run it through that
before submitting it again.
I'll not take this version for the above reasons.
thanks,
greg k-h
next prev parent reply other threads:[~2009-10-06 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 20:45 [PATCH] Changes to integrate RAR with SEP and fix RAR problems Mark Allyn
2009-10-06 21:29 ` Greg KH [this message]
2009-10-06 22:22 ` Alan Cox
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=20091006212936.GA21996@kroah.com \
--to=greg@kroah.com \
--cc=alan@linux.intel.com \
--cc=charles.f.johnson@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.a.allyn@intel.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