Re: [PATCH v2 4/5] soc: qcom: Remote FS memory driver

On Mon, Aug 07, 2017 at 09:23:27AM -0700, Bjorn Andersson wrote:

Up until this patch the user space tool that implements the message
handler just mapped the reserved memory region though /dev/mem, but this
requires /dev/mem access and for the later platforms we need to make a
call into TrustZone to provide the remote permission to access this
memory region. So we need some code in the kernel to represent this.

quoted

Else: NAK as the scheme looks completely brain dead and bonkers.

I can rework the commit message in an attempt to better explain the
setup and hope you/people find it slightly less bonkers.

Does this sound reasonable?

Please rework the commit message.  And it should probably grow a saner
module name, too.