On Mon, May 08, 2017 at 09:46:41PM +0530, Jagan Teki wrote:
> Hi Tom,
>
> Please take this PR.
>
> thanks!
> Jagan.
>
> The following changes since commit ac6991fb5fc1a694b29f4ebd5e07baebf818d7cc:
>
> zynq: spi: Honour the activation / deactivation delay (2017-05-03 11:03:04
> +0530)
>
> a
On 3 January 2016 at 21:26, Tom Rini wrote:
> On Sun, Jan 03, 2016 at 09:10:14PM +0530, Jagan Teki wrote:
>> On 3 January 2016 at 20:14, Tom Rini wrote:
>> > On Sun, Jan 03, 2016 at 09:26:38AM +0530, Jagan Teki wrote:
>> >> On 2 January 2016 at 22:34, Tom Rini wrote:
>> >> > On Wed, Dec 30, 2015
On Sun, Jan 03, 2016 at 09:10:14PM +0530, Jagan Teki wrote:
> On 3 January 2016 at 20:14, Tom Rini wrote:
> > On Sun, Jan 03, 2016 at 09:26:38AM +0530, Jagan Teki wrote:
> >> On 2 January 2016 at 22:34, Tom Rini wrote:
> >> > On Wed, Dec 30, 2015 at 04:04:23PM +0530, Jagan Teki wrote:
> >> >
> >>
On 3 January 2016 at 20:14, Tom Rini wrote:
> On Sun, Jan 03, 2016 at 09:26:38AM +0530, Jagan Teki wrote:
>> On 2 January 2016 at 22:34, Tom Rini wrote:
>> > On Wed, Dec 30, 2015 at 04:04:23PM +0530, Jagan Teki wrote:
>> >
>> >> Tom,
>> >>
>> >> Please note that subject shows u-boot-spi/next but
On Sun, Jan 03, 2016 at 09:26:38AM +0530, Jagan Teki wrote:
> On 2 January 2016 at 22:34, Tom Rini wrote:
> > On Wed, Dec 30, 2015 at 04:04:23PM +0530, Jagan Teki wrote:
> >
> >> Tom,
> >>
> >> Please note that subject shows u-boot-spi/next but it actually
> >> u-boot-spi/master and of course PR s
On 2 January 2016 at 22:34, Tom Rini wrote:
> On Wed, Dec 30, 2015 at 04:04:23PM +0530, Jagan Teki wrote:
>
>> Tom,
>>
>> Please note that subject shows u-boot-spi/next but it actually
>> u-boot-spi/master and of course PR shows the repo as master (not
>> next).
>
> OK, what in here is a clear bug
On Wed, Dec 30, 2015 at 04:04:23PM +0530, Jagan Teki wrote:
> Tom,
>
> Please note that subject shows u-boot-spi/next but it actually
> u-boot-spi/master and of course PR shows the repo as master (not
> next).
OK, what in here is a clear bugfix rather than new feature that we
should have taken i
On 30 December 2015 at 16:04, Jagan Teki wrote:
> Tom,
Please pull this asap, in case if you miss.
>
> Please note that subject shows u-boot-spi/next but it actually
> u-boot-spi/master and of course PR shows the repo as master (not
> next).
>
> On 30 December 2015 at 16:01, Jagan Teki wrote:
>
Tom,
Please note that subject shows u-boot-spi/next but it actually
u-boot-spi/master and of course PR shows the repo as master (not
next).
On 30 December 2015 at 16:01, Jagan Teki wrote:
> Hi Tom,
>
> Please pull this PR.
>
> thanks!
> Jagan.
>
> The following changes since commit 312db9f75f50b
On Wed, Nov 4, 2015 at 9:35 AM, Fabio Estevam wrote:
> After applying this size_t change plus the three attached bitops
> patches I sent you for mips, arc. avr32 I do not see any more build
> issues here.
>
> Also, when you apply the three patches to your tree, please make sure
> they are applied
On Wed, Nov 4, 2015 at 9:30 AM, Jagan Teki wrote:
> Yes true, stm_lock and stm_unlock should use size_t for len - Will
> update the same.
>
> With these all built fine?
After applying this size_t change plus the three attached bitops
patches I sent you for mips, arc. avr32 I do not see any more
On 4 November 2015 at 16:51, Fabio Estevam wrote:
> Hi Jagan,
>
> On Wed, Nov 4, 2015 at 9:17 AM, Jagan Teki wrote:
>
>> Updated u32 to size_t as prototype uses the same. Does this break? it look
>> OK?
>
> Here is the error I see on Blackfin:
>
> Building bf518f-ezbrd board...
> /home/fabio/.bu
Hi Jagan,
On Wed, Nov 4, 2015 at 9:17 AM, Jagan Teki wrote:
> Updated u32 to size_t as prototype uses the same. Does this break? it look OK?
Here is the error I see on Blackfin:
Building bf518f-ezbrd board...
/home/fabio/.buildman-toolchains/gcc-4.6.3-nolibc/bfin-uclinux/bin/bfin-uclinux-size:
Fabio,
On 4 November 2015 at 16:38, Fabio Estevam wrote:
> Hi Jagan,
>
> On Wed, Nov 4, 2015 at 8:47 AM, Fabio Estevam wrote:
>> On Wed, Nov 4, 2015 at 8:46 AM, Fabio Estevam wrote:
>>> Hi Tom,
>>>
>>> On Wed, Nov 4, 2015 at 1:45 AM, Fabio Estevam wrote:
On Tue, Nov 3, 2015 at 11:47 PM, T
Hi Jagan,
On Wed, Nov 4, 2015 at 8:47 AM, Fabio Estevam wrote:
> On Wed, Nov 4, 2015 at 8:46 AM, Fabio Estevam wrote:
>> Hi Tom,
>>
>> On Wed, Nov 4, 2015 at 1:45 AM, Fabio Estevam wrote:
>>> On Tue, Nov 3, 2015 at 11:47 PM, Tom Rini wrote:
>>>
NAK.
So, this blows up badly for a
On Wed, Nov 4, 2015 at 8:46 AM, Fabio Estevam wrote:
> Hi Tom,
>
> On Wed, Nov 4, 2015 at 1:45 AM, Fabio Estevam wrote:
>> On Tue, Nov 3, 2015 at 11:47 PM, Tom Rini wrote:
>>
>>> NAK.
>>>
>>> So, this blows up badly for a lot of things when I do:
>>> ./tools/buildman/buildman -b master --force-b
Hi Tom,
On Wed, Nov 4, 2015 at 1:45 AM, Fabio Estevam wrote:
> On Tue, Nov 3, 2015 at 11:47 PM, Tom Rini wrote:
>
>> NAK.
>>
>> So, this blows up badly for a lot of things when I do:
>> ./tools/buildman/buildman -b master --force-build --step 0 -Cdvel
>> 'blackfin|microblaze|m68k|nds32|x86|aarch
On Tue, Nov 3, 2015 at 11:47 PM, Tom Rini wrote:
> NAK.
>
> So, this blows up badly for a lot of things when I do:
> ./tools/buildman/buildman -b master --force-build --step 0 -Cdvel
> 'blackfin|microblaze|m68k|nds32|x86|aarch64|sandbox|mips|avr32|arm|powerpc|sh4|sparc'
It seems I missed to add
Hi Jagan,
On Wed, Nov 4, 2015 at 9:47 AM, Tom Rini wrote:
> On Tue, Nov 03, 2015 at 11:39:56PM +0530, Jagan Teki wrote:
>
>> Hi Tom,
>>
>> Please pull this series.
>>
>> thanks!
>> Jagan.
>>
>> The following changes since commit 96d59e9d6aa74e35c63dc74da10e41f8ba0f6de4:
>>
>> mpc85xx/t2081: ena
On Tue, Nov 03, 2015 at 11:39:56PM +0530, Jagan Teki wrote:
> Hi Tom,
>
> Please pull this series.
>
> thanks!
> Jagan.
>
> The following changes since commit 96d59e9d6aa74e35c63dc74da10e41f8ba0f6de4:
>
> mpc85xx/t2081: enable parsing DDR ratio for T2081 rev1.1 (2015-11-02
> 08:51:50 -0800)
20 matches
Mail list logo
