Hi,
I think we should move the generic TEE subsystem to /drivers/tee and /include/linux/tee since we're only dealing with TEE.
What do you think should we move from sec-hw to tee?
Regards, Jens
Hi,
On 09 Apr 2015, at 10:57, Jens Wiklander jens.wiklander@linaro.org wrote:
Hi,
I think we should move the generic TEE subsystem to /drivers/tee and /include/linux/tee since we're only dealing with TEE.
+1
What do you think should we move from sec-hw to tee?
As I mentioned before, we are moving towards a tee driver in the end, so I support this change. If we move it, should I also move github to a tee project? The sooner the better.
Regards, Jens _______________________________________________ Tee-dev mailing list Tee-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/tee-dev
Best, Javier
p.s. Jens, I will send some feedback to the patches later today :)
Hi Javier and Jens,
On Thu, Apr 09, 2015 at 11:01:17AM +0200, javigon wrote:
Hi,
On 09 Apr 2015, at 10:57, Jens Wiklander jens.wiklander@linaro.org wrote:
Hi,
I think we should move the generic TEE subsystem to /drivers/tee and /include/linux/tee since we're only dealing with TEE.
+1
+1
What do you think should we move from sec-hw to tee?
As I mentioned before, we are moving towards a tee driver in the end, so I support this change. If we move it, should I also move github to a tee project? The sooner the better.
My take is that as soon as patches has been accepted upstream, then we don't need any GitHub project any longer, or?
Regards, Jens
Best, Javier
Hi,
On 09 Apr 2015, at 11:12, Joakim Bech joakim.bech@linaro.org wrote:
Hi Javier and Jens,
On Thu, Apr 09, 2015 at 11:01:17AM +0200, javigon wrote:
Hi,
On 09 Apr 2015, at 10:57, Jens Wiklander jens.wiklander@linaro.org wrote:
Hi,
I think we should move the generic TEE subsystem to /drivers/tee and /include/linux/tee since we're only dealing with TEE.
+1
+1
What do you think should we move from sec-hw to tee?
As I mentioned before, we are moving towards a tee driver in the end, so I support this change. If we move it, should I also move github to a tee project? The sooner the better.
My take is that as soon as patches has been accepted upstream, then we don't need any GitHub project any longer, or?
I guess it depends on how much we plan on developing after the first round. I intend to merge the OTZ driver and the kernel interface - github seems like a natural place.
Regards, Jens
Best, Javier
-- Regards, Joakim B
Best, Javier
Hi,
On Thu, Apr 09, 2015 at 11:22:12AM +0200, javigon wrote:
What do you think should we move from sec-hw to tee?
As I mentioned before, we are moving towards a tee driver in the end, so I support this change. If we move it, should I also move github to a tee project? The sooner the better.
My take is that as soon as patches has been accepted upstream, then we don't need any GitHub project any longer, or?
I guess it depends on how much we plan on developing after the first round. I intend to merge the OTZ driver and the kernel interface - github seems like a natural place.
Ok, got it, it might make sense to still have somewhere where we can prototype new stuff before sending it upstream, however I think we (Linaro) will try to as much as possible to send patches in the future directly to upstream.
Regards, Jens
Best, Javier
-- Regards, Joakim B
Best, Javier
Hi,
On 09 Apr 2015, at 11:29, Joakim Bech joakim.bech@linaro.org wrote:
Hi,
On Thu, Apr 09, 2015 at 11:22:12AM +0200, javigon wrote:
What do you think should we move from sec-hw to tee?
As I mentioned before, we are moving towards a tee driver in the end, so I support this change. If we move it, should I also move github to a tee project? The sooner the better.
My take is that as soon as patches has been accepted upstream, then we don't need any GitHub project any longer, or?
I guess it depends on how much we plan on developing after the first round. I intend to merge the OTZ driver and the kernel interface - github seems like a natural place.
Ok, got it, it might make sense to still have somewhere where we can prototype new stuff before sending it upstream, however I think we (Linaro) will try to as much as possible to send patches in the future directly to upstream.
Makes sense. I will then keep the github as it is, and we see how it develops when the first patchset has been accepted.
Regards, Jens
Best, Javier
-- Regards, Joakim B
Best, Javier
-- Regards, Joakim B
Best, Javier
-
javigon -
Jens Wiklander -
Joakim Bech