On Fri, Jun 26, 2020 at 08:11:21AM -0700, James Bottomley wrote:
> On Fri, 2020-06-26 at 12:29 +0100, Daniel Thompson wrote:
> > On Fri, Jun 26, 2020 at 10:40:41AM +0530, Sumit Garg wrote:
> > > On Fri, 26 Jun 2020 at 05:01, James Bottomley
> > > wrote:
> > > >
> > > > On Thu, 2020-06-25 at 19:54
On Fri, 26 Jun 2020 at 20:41, James Bottomley
wrote:
>
> On Fri, 2020-06-26 at 12:29 +0100, Daniel Thompson wrote:
> > On Fri, Jun 26, 2020 at 10:40:41AM +0530, Sumit Garg wrote:
> > > On Fri, 26 Jun 2020 at 05:01, James Bottomley
> > > wrote:
> > > >
> > > > On Thu, 2020-06-25 at 19:54 +0530, Su
On Fri, 2020-06-26 at 12:29 +0100, Daniel Thompson wrote:
> On Fri, Jun 26, 2020 at 10:40:41AM +0530, Sumit Garg wrote:
> > On Fri, 26 Jun 2020 at 05:01, James Bottomley
> > wrote:
> > >
> > > On Thu, 2020-06-25 at 19:54 +0530, Sumit Garg wrote:
> > > > On Wed, 24 Jun 2020 at 20:51, James Bottoml
On Fri, Jun 26, 2020 at 10:40:41AM +0530, Sumit Garg wrote:
> On Fri, 26 Jun 2020 at 05:01, James Bottomley
> wrote:
> >
> > On Thu, 2020-06-25 at 19:54 +0530, Sumit Garg wrote:
> > > On Wed, 24 Jun 2020 at 20:51, James Bottomley
> > > wrote:
> > > >
> > > > On Wed, 2020-06-24 at 16:17 +0530, Sum
On Fri, Jun 26, 2020 at 8:18 AM Sumit Garg wrote:
> On Thu, 25 Jun 2020 at 18:22, Maxim Uvarov wrote:
...
> I guess you missed the point that uuid_t is implemented in BE format
> in the kernel which is compliant as per RFC 4122.
I guess you missed the point. Kernel doesn't have anything specia
On Fri, 26 Jun 2020 at 10:40, Sumit Garg wrote:
>
> On Fri, 26 Jun 2020 at 05:01, James Bottomley
> wrote:
> >
> > On Thu, 2020-06-25 at 19:54 +0530, Sumit Garg wrote:
> > > On Wed, 24 Jun 2020 at 20:51, James Bottomley
> > > wrote:
> > > >
> > > > On Wed, 2020-06-24 at 16:17 +0530, Sumit Garg w
On Thu, 25 Jun 2020 at 18:22, Maxim Uvarov wrote:
>
> On Wed, 24 Jun 2020 at 18:44, Jerome Forissier wrote:
> >
> >
> >
> > On 6/24/20 5:21 PM, James Bottomley wrote:
> > > On Wed, 2020-06-24 at 16:17 +0530, Sumit Garg wrote:
> > >> Apologies for delay in my reply as I was busy with some other st
On Thu, 25 Jun 2020 at 18:22, Maxim Uvarov wrote:
>
> On Wed, 24 Jun 2020 at 18:44, Jerome Forissier wrote:
> >
> >
> >
> > On 6/24/20 5:21 PM, James Bottomley wrote:
> > > On Wed, 2020-06-24 at 16:17 +0530, Sumit Garg wrote:
> > >> Apologies for delay in my reply as I was busy with some other st
On Fri, 26 Jun 2020 at 05:01, James Bottomley
wrote:
>
> On Thu, 2020-06-25 at 19:54 +0530, Sumit Garg wrote:
> > On Wed, 24 Jun 2020 at 20:51, James Bottomley
> > wrote:
> > >
> > > On Wed, 2020-06-24 at 16:17 +0530, Sumit Garg wrote:
> > > > Apologies for delay in my reply as I was busy with so
On Thu, 2020-06-25 at 19:54 +0530, Sumit Garg wrote:
> On Wed, 24 Jun 2020 at 20:51, James Bottomley
> wrote:
> >
> > On Wed, 2020-06-24 at 16:17 +0530, Sumit Garg wrote:
> > > Apologies for delay in my reply as I was busy with some other
> > > stuff.
> > >
> > > On Fri, 19 Jun 2020 at 20:30, Ja
On Wed, 24 Jun 2020 at 20:51, James Bottomley
wrote:
>
> On Wed, 2020-06-24 at 16:17 +0530, Sumit Garg wrote:
> > Apologies for delay in my reply as I was busy with some other stuff.
> >
> > On Fri, 19 Jun 2020 at 20:30, James Bottomley
> > wrote:
> [...]
> > > it's about consistency with what th
On Wed, 24 Jun 2020 at 18:44, Jerome Forissier wrote:
>
>
>
> On 6/24/20 5:21 PM, James Bottomley wrote:
> > On Wed, 2020-06-24 at 16:17 +0530, Sumit Garg wrote:
> >> Apologies for delay in my reply as I was busy with some other stuff.
> >>
> >> On Fri, 19 Jun 2020 at 20:30, James Bottomley
> >>
On 6/24/20 5:21 PM, James Bottomley wrote:
> On Wed, 2020-06-24 at 16:17 +0530, Sumit Garg wrote:
>> Apologies for delay in my reply as I was busy with some other stuff.
>>
>> On Fri, 19 Jun 2020 at 20:30, James Bottomley
>> wrote:
> [...]
>>> it's about consistency with what the kernel types m
On Wed, 2020-06-24 at 16:17 +0530, Sumit Garg wrote:
> Apologies for delay in my reply as I was busy with some other stuff.
>
> On Fri, 19 Jun 2020 at 20:30, James Bottomley
> wrote:
[...]
> > it's about consistency with what the kernel types mean. When some
> > checker detects your using little
Apologies for delay in my reply as I was busy with some other stuff.
On Fri, 19 Jun 2020 at 20:30, James Bottomley
wrote:
>
> On Fri, 2020-06-19 at 13:42 +0530, Sumit Garg wrote:
> > On Fri, 19 Jun 2020 at 00:49, James Bottomley
> > wrote:
> > >
> > > On Thu, 2020-06-18 at 10:42 +0530, Sumit Gar
On Fri, Jun 19, 2020 at 08:00:44AM -0700, James Bottomley wrote:
> On Fri, 2020-06-19 at 13:42 +0530, Sumit Garg wrote:
> > On Fri, 19 Jun 2020 at 00:49, James Bottomley
> > wrote:
> > >
> > > On Thu, 2020-06-18 at 10:42 +0530, Sumit Garg wrote:
> > > > On Thu, 18 Jun 2020 at 10:29, Sumit Garg
>
On Fri, 2020-06-19 at 13:42 +0530, Sumit Garg wrote:
> On Fri, 19 Jun 2020 at 00:49, James Bottomley
> wrote:
> >
> > On Thu, 2020-06-18 at 10:42 +0530, Sumit Garg wrote:
> > > On Thu, 18 Jun 2020 at 10:29, Sumit Garg
> > > wrote:
> >
> > [...]
> > > > > typedef struct
> > > > > {
> > > > >
On Fri, 19 Jun 2020 at 00:49, James Bottomley
wrote:
>
> On Thu, 2020-06-18 at 10:42 +0530, Sumit Garg wrote:
> > On Thu, 18 Jun 2020 at 10:29, Sumit Garg
> > wrote:
> [...]
> > > > typedef struct
> > > > {
> > > > uint32_t timeLow;
> > > > uint16_t timeMid;
> > > > uint16
On Thu, 2020-06-18 at 10:42 +0530, Sumit Garg wrote:
> On Thu, 18 Jun 2020 at 10:29, Sumit Garg
> wrote:
[...]
> > > typedef struct
> > > {
> > > uint32_t timeLow;
> > > uint16_t timeMid;
> > > uint16_t timeHiAndVersion;
> > > uint8_t clockSeqAndNode[8];
> > > } TEE
There was a comment about a new mailing list address in Documentation.
Which one I should specify now?
On Thu, 18 Jun 2020 at 09:57, Jerome Forissier wrote:
>
> On 6/18/20 6:59 AM, Sumit Garg wrote:
> > Hi Jerome,
> >
> > On Wed, 17 Jun 2020 at 20:46, Jerome Forissier wrote:
> >>
> >>
> >>
> >>
On 6/18/20 6:59 AM, Sumit Garg wrote:
> Hi Jerome,
>
> On Wed, 17 Jun 2020 at 20:46, Jerome Forissier wrote:
>>
>>
>>
>> On 6/17/20 3:58 PM, Sumit Garg wrote:
>>> Hi Maxim,
>>>
>>> On Thu, 4 Jun 2020 at 23:28, Maxim Uvarov wrote:
With the evolving use-cases for TEE bus, now it's requir
On Thu, 18 Jun 2020 at 10:29, Sumit Garg wrote:
>
> Hi Jerome,
>
> On Wed, 17 Jun 2020 at 20:46, Jerome Forissier wrote:
> >
> >
> >
> > On 6/17/20 3:58 PM, Sumit Garg wrote:
> > > Hi Maxim,
> > >
> > > On Thu, 4 Jun 2020 at 23:28, Maxim Uvarov wrote:
> > >>
> > >> With the evolving use-cases fo
Hi Jerome,
On Wed, 17 Jun 2020 at 20:46, Jerome Forissier wrote:
>
>
>
> On 6/17/20 3:58 PM, Sumit Garg wrote:
> > Hi Maxim,
> >
> > On Thu, 4 Jun 2020 at 23:28, Maxim Uvarov wrote:
> >>
> >> With the evolving use-cases for TEE bus, now it's required to support
> >> multi-stage enumeration proce
On 6/17/20 9:52 PM, Maxim Uvarov wrote:
> On Wed, 17 Jun 2020 at 18:16, Jerome Forissier wrote:
>>
>> On 6/17/20 3:58 PM, Sumit Garg wrote:
>>> Hi Maxim,
>>>
>>> On Thu, 4 Jun 2020 at 23:28, Maxim Uvarov wrote:
With the evolving use-cases for TEE bus, now it's required to support
m
On Wed, 17 Jun 2020 at 18:16, Jerome Forissier wrote:
>
>
>
> On 6/17/20 3:58 PM, Sumit Garg wrote:
> > Hi Maxim,
> >
> > On Thu, 4 Jun 2020 at 23:28, Maxim Uvarov wrote:
> >>
> >> With the evolving use-cases for TEE bus, now it's required to support
> >> multi-stage enumeration process. But usin
On 6/17/20 3:58 PM, Sumit Garg wrote:
> Hi Maxim,
>
> On Thu, 4 Jun 2020 at 23:28, Maxim Uvarov wrote:
>>
>> With the evolving use-cases for TEE bus, now it's required to support
>> multi-stage enumeration process. But using a simple index doesn't
>> suffice this requirement and instead leads
On Wed, 17 Jun 2020 at 16:58, Sumit Garg wrote:
>
> Hi Maxim,
>
> On Thu, 4 Jun 2020 at 23:28, Maxim Uvarov wrote:
> >
> > With the evolving use-cases for TEE bus, now it's required to support
> > multi-stage enumeration process. But using a simple index doesn't
> > suffice this requirement and i
Hi Maxim,
On Thu, 4 Jun 2020 at 23:28, Maxim Uvarov wrote:
>
> With the evolving use-cases for TEE bus, now it's required to support
> multi-stage enumeration process. But using a simple index doesn't
> suffice this requirement and instead leads to duplicate sysfs entries.
> So instead switch to
On Wed, 17 Jun 2020 at 09:07, Sumit Garg wrote:
>
> On Wed, 17 Jun 2020 at 02:20, Jarkko Sakkinen
> wrote:
> >
> > On Thu, Jun 04, 2020 at 08:58:49PM +0300, Maxim Uvarov wrote:
> > > With the evolving use-cases for TEE bus, now it's required to support
> > > multi-stage enumeration process. But u
On Wed, 17 Jun 2020 at 02:20, Jarkko Sakkinen
wrote:
>
> On Thu, Jun 04, 2020 at 08:58:49PM +0300, Maxim Uvarov wrote:
> > With the evolving use-cases for TEE bus, now it's required to support
> > multi-stage enumeration process. But using a simple index doesn't
> > suffice this requirement and in
On Thu, Jun 04, 2020 at 08:58:49PM +0300, Maxim Uvarov wrote:
> With the evolving use-cases for TEE bus, now it's required to support
> multi-stage enumeration process. But using a simple index doesn't
> suffice this requirement and instead leads to duplicate sysfs entries.
> So instead switch to u
With the evolving use-cases for TEE bus, now it's required to support
multi-stage enumeration process. But using a simple index doesn't
suffice this requirement and instead leads to duplicate sysfs entries.
So instead switch to use more informative device UUID for sysfs entry
like:
/sys/bus/tee/dev
32 matches
Mail list logo
