Re: [PATCH v2 1/4] remoteproc: Keep local copy of firmware name

2016-10-18 Thread Bjorn Andersson
On Mon 17 Oct 08:48 PDT 2016, Matt Redfearn wrote: > Storage of the firmware name was inconsistent, either storing a pointer > to a name stored with unknown ownership, or a variable length tacked > onto the end of the struct proc allocated in rproc_alloc. > > In preparation for allowing the

Re: [PATCH v2 1/4] remoteproc: Keep local copy of firmware name

2016-10-18 Thread Bjorn Andersson
On Mon 17 Oct 08:48 PDT 2016, Matt Redfearn wrote: > Storage of the firmware name was inconsistent, either storing a pointer > to a name stored with unknown ownership, or a variable length tacked > onto the end of the struct proc allocated in rproc_alloc. > > In preparation for allowing the

[PATCH v2 1/4] remoteproc: Keep local copy of firmware name

2016-10-17 Thread Matt Redfearn
Storage of the firmware name was inconsistent, either storing a pointer to a name stored with unknown ownership, or a variable length tacked onto the end of the struct proc allocated in rproc_alloc. In preparation for allowing the firmware of an already allocated struct rproc to be changed,

[PATCH v2 1/4] remoteproc: Keep local copy of firmware name

2016-10-17 Thread Matt Redfearn
Storage of the firmware name was inconsistent, either storing a pointer to a name stored with unknown ownership, or a variable length tacked onto the end of the struct proc allocated in rproc_alloc. In preparation for allowing the firmware of an already allocated struct rproc to be changed,