On 12 March 2016 at 20:07, Jagan Teki wrote:
> Hi Marek,
>
> On 12 March 2016 at 00:29, Marek Vasut wrote:
>> On 03/11/2016 07:44 PM, Jagan Teki wrote:
>>> On 12 March 2016 at 00:03, Marek Vasut wrote:
On 03/11/2016 07:07 PM, Jagan
Hi Marek,
On 12 March 2016 at 00:29, Marek Vasut wrote:
> On 03/11/2016 07:44 PM, Jagan Teki wrote:
>> On 12 March 2016 at 00:03, Marek Vasut wrote:
>>> On 03/11/2016 07:07 PM, Jagan Teki wrote:
On 11 March 2016 at 23:32, Marek Vasut wrote:
Hi Albert,
On 12 March 2016 at 01:04, Albert ARIBAUD wrote:
> Hello Jagan,
>
> On Sat, 12 Mar 2016 00:41:25 +0530, Jagan Teki
> wrote:
>> Hi Albert,
>>
>> On 12 March 2016 at 00:17, Albert ARIBAUD wrote:
>> > Hello
Hello Jagan,
On Sat, 12 Mar 2016 00:41:25 +0530, Jagan Teki
wrote:
> Hi Albert,
>
> On 12 March 2016 at 00:17, Albert ARIBAUD wrote:
> > Hello Jagan,
> >
> > On Fri, 11 Mar 2016 12:09:37 +0530, Jagan Teki
> >
Hi Albert,
On 12 March 2016 at 00:17, Albert ARIBAUD wrote:
> Hello Jagan,
>
> On Fri, 11 Mar 2016 12:09:37 +0530, Jagan Teki
> wrote:
>> On 11 March 2016 at 07:50, Marek Vasut wrote:
>> > The stm_is_locked_sr() function is
Hello Jagan,
On Fri, 11 Mar 2016 12:09:37 +0530, Jagan Teki
wrote:
> On 11 March 2016 at 07:50, Marek Vasut wrote:
> > The stm_is_locked_sr() function is picked from Linux kernel. For reason
> > unknown, the 64bit data types used by the function and
On 03/11/2016 07:44 PM, Jagan Teki wrote:
> On 12 March 2016 at 00:03, Marek Vasut wrote:
>> On 03/11/2016 07:07 PM, Jagan Teki wrote:
>>> On 11 March 2016 at 23:32, Marek Vasut wrote:
On 03/11/2016 06:34 PM, Jagan Teki wrote:
> On 11 March 2016 at 17:59,
On 12 March 2016 at 00:03, Marek Vasut wrote:
> On 03/11/2016 07:07 PM, Jagan Teki wrote:
>> On 11 March 2016 at 23:32, Marek Vasut wrote:
>>> On 03/11/2016 06:34 PM, Jagan Teki wrote:
On 11 March 2016 at 17:59, Marek Vasut wrote:
> On
On 03/11/2016 07:07 PM, Jagan Teki wrote:
> On 11 March 2016 at 23:32, Marek Vasut wrote:
>> On 03/11/2016 06:34 PM, Jagan Teki wrote:
>>> On 11 March 2016 at 17:59, Marek Vasut wrote:
On 03/11/2016 07:39 AM, Jagan Teki wrote:
> On 11 March 2016 at 07:50,
On 11 March 2016 at 23:32, Marek Vasut wrote:
> On 03/11/2016 06:34 PM, Jagan Teki wrote:
>> On 11 March 2016 at 17:59, Marek Vasut wrote:
>>> On 03/11/2016 07:39 AM, Jagan Teki wrote:
On 11 March 2016 at 07:50, Marek Vasut wrote:
> The
On 03/11/2016 06:34 PM, Jagan Teki wrote:
> On 11 March 2016 at 17:59, Marek Vasut wrote:
>> On 03/11/2016 07:39 AM, Jagan Teki wrote:
>>> On 11 March 2016 at 07:50, Marek Vasut wrote:
The stm_is_locked_sr() function is picked from Linux kernel. For reason
On 11 March 2016 at 17:59, Marek Vasut wrote:
> On 03/11/2016 07:39 AM, Jagan Teki wrote:
>> On 11 March 2016 at 07:50, Marek Vasut wrote:
>>> The stm_is_locked_sr() function is picked from Linux kernel. For reason
>>> unknown, the 64bit data types used by the
On 03/11/2016 07:39 AM, Jagan Teki wrote:
> On 11 March 2016 at 07:50, Marek Vasut wrote:
>> The stm_is_locked_sr() function is picked from Linux kernel. For reason
>> unknown, the 64bit data types used by the function and present in Linux
>> were replaced with 32bit unsigned ones,
On 11 March 2016 at 07:50, Marek Vasut wrote:
> The stm_is_locked_sr() function is picked from Linux kernel. For reason
> unknown, the 64bit data types used by the function and present in Linux
> were replaced with 32bit unsigned ones, which causes trouble.
>
> The testcase
The stm_is_locked_sr() function is picked from Linux kernel. For reason
unknown, the 64bit data types used by the function and present in Linux
were replaced with 32bit unsigned ones, which causes trouble.
The testcase performed was done using ST M25P80 chip.
The command used was:
=> sf protect
15 matches
Mail list logo