Hi,
On Thu, Dec 18, 2014 at 09:55:10AM +0100, Robert Baldyga wrote:
Since we can compose gadgets from many functions, there is the problem
related to gadget breakage while FunctionFS daemon being closed. FFS
function is userspace code so there is no way to know when it will close
files (it
On Thu, Dec 18 2014, Robert Baldyga wrote:
Since we can compose gadgets from many functions, there is the problem
related to gadget breakage while FunctionFS daemon being closed. FFS
function is userspace code so there is no way to know when it will close
files (it doesn't matter what is the
On Thu, Dec 18, 2014 at 09:55:10AM +0100, Robert Baldyga wrote:
Since we can compose gadgets from many functions, there is the problem
related to gadget breakage while FunctionFS daemon being closed. FFS
function is userspace code so there is no way to know when it will close
files (it doesn't
On Tue, Dec 23, 2014 at 12:48:58PM -0600, Felipe Balbi wrote:
On Thu, Dec 18, 2014 at 09:55:10AM +0100, Robert Baldyga wrote:
Since we can compose gadgets from many functions, there is the problem
related to gadget breakage while FunctionFS daemon being closed. FFS
function is userspace
On Tue, Dec 23, 2014 at 12:47:55PM -0800, David Cohen wrote:
On Tue, Dec 23, 2014 at 12:48:58PM -0600, Felipe Balbi wrote:
On Thu, Dec 18, 2014 at 09:55:10AM +0100, Robert Baldyga wrote:
Since we can compose gadgets from many functions, there is the problem
related to gadget breakage
Since we can compose gadgets from many functions, there is the problem
related to gadget breakage while FunctionFS daemon being closed. FFS
function is userspace code so there is no way to know when it will close
files (it doesn't matter what is the reason of this situation, it can
be daemon