(2013/03/20 1:43), Gregory CLEMENT wrote:
> Hi Masami,
>
> You can try this patch if you want.
> I don't have the hardware today so I didn't test it.
> If you (and also Florian and Ezequiel) can test it and if it fixed
> the bug, then I will be able send a proper email for it,
Hi Gregory,
Thank
On 03/19/2013 08:48 PM, Florian Fainelli wrote:
> On Tuesday 19 March 2013 17:43:49 Gregory CLEMENT wrote:
>>
>> Hi Masami,
>>
>> You can try this patch if you want.
>> I don't have the hardware today so I didn't test it.
>> If you (and also Florian and Ezequiel) can test it and if it fixed
>> the
On 03/19/2013 08:48 PM, Florian Fainelli wrote:
On Tuesday 19 March 2013 17:43:49 Gregory CLEMENT wrote:
Hi Masami,
You can try this patch if you want.
I don't have the hardware today so I didn't test it.
If you (and also Florian and Ezequiel) can test it and if it fixed
the bug, then I
(2013/03/20 1:43), Gregory CLEMENT wrote:
Hi Masami,
You can try this patch if you want.
I don't have the hardware today so I didn't test it.
If you (and also Florian and Ezequiel) can test it and if it fixed
the bug, then I will be able send a proper email for it,
Hi Gregory,
Thank you
Hi Gregory,
>On 03/19/2013 05:43 PM, Gregory CLEMENT wrote:
>> On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
>>>
>>> Here I've hit a bug on the recent kernel. As far as I know, this bug
>>> exists on 3.9-rc1 too.
>>>
>>> When I tried the latest mvebu for-next tree
>>>
On Tuesday 19 March 2013 17:43:49 Gregory CLEMENT wrote:
>
> Hi Masami,
>
> You can try this patch if you want.
> I don't have the hardware today so I didn't test it.
> If you (and also Florian and Ezequiel) can test it and if it fixed
> the bug, then I will be able send a proper email for it,
On 03/19/2013 03:19 PM, Masami Hiramatsu wrote:
> Hi Ezequiel,
>
> (2013/03/19 22:39), Ezequiel Garcia wrote:
>> Hi Masami,
>>
>> On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
>>>
>>> Here I've hit a bug on the recent kernel. As far as I know, this bug
>>> exists on 3.9-rc1
On Tue, Mar 19, 2013 at 11:19:05PM +0900, Masami Hiramatsu wrote:
> Hi Jason,
>
> (2013/03/19 22:33), Jason Cooper wrote:
> > On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
> >> Hi,
> >>
> >> Here I've hit a bug on the recent kernel. As far as I know, this bug
> >> exists on
Hi Ezequiel,
(2013/03/19 22:39), Ezequiel Garcia wrote:
> Hi Masami,
>
> On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
>>
>> Here I've hit a bug on the recent kernel. As far as I know, this bug
>> exists on 3.9-rc1 too.
>>
>> When I tried the latest mvebu for-next tree
>>
Hi Jason,
(2013/03/19 22:33), Jason Cooper wrote:
> On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
>> Hi,
>>
>> Here I've hit a bug on the recent kernel. As far as I know, this bug
>> exists on 3.9-rc1 too.
>>
>> When I tried the latest mvebu for-next tree
>>
Hi Masami,
On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
>
> Here I've hit a bug on the recent kernel. As far as I know, this bug
> exists on 3.9-rc1 too.
>
> When I tried the latest mvebu for-next tree
> (git://git.infradead.org/users/jcooper/linux.git mvebu/for-next),
> I
On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
> Hi,
>
> Here I've hit a bug on the recent kernel. As far as I know, this bug
> exists on 3.9-rc1 too.
>
> When I tried the latest mvebu for-next tree
> (git://git.infradead.org/users/jcooper/linux.git mvebu/for-next),
FYI: that
Hi,
Here I've hit a bug on the recent kernel. As far as I know, this bug
exists on 3.9-rc1 too.
When I tried the latest mvebu for-next tree
(git://git.infradead.org/users/jcooper/linux.git mvebu/for-next),
I got below warning at bootup time and mvneta didn't work (link was never up).
I ensured
Hi,
Here I've hit a bug on the recent kernel. As far as I know, this bug
exists on 3.9-rc1 too.
When I tried the latest mvebu for-next tree
(git://git.infradead.org/users/jcooper/linux.git mvebu/for-next),
I got below warning at bootup time and mvneta didn't work (link was never up).
I ensured
On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
Hi,
Here I've hit a bug on the recent kernel. As far as I know, this bug
exists on 3.9-rc1 too.
When I tried the latest mvebu for-next tree
(git://git.infradead.org/users/jcooper/linux.git mvebu/for-next),
FYI: that branch
Hi Masami,
On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
Here I've hit a bug on the recent kernel. As far as I know, this bug
exists on 3.9-rc1 too.
When I tried the latest mvebu for-next tree
(git://git.infradead.org/users/jcooper/linux.git mvebu/for-next),
I got
Hi Jason,
(2013/03/19 22:33), Jason Cooper wrote:
On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
Hi,
Here I've hit a bug on the recent kernel. As far as I know, this bug
exists on 3.9-rc1 too.
When I tried the latest mvebu for-next tree
Hi Ezequiel,
(2013/03/19 22:39), Ezequiel Garcia wrote:
Hi Masami,
On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
Here I've hit a bug on the recent kernel. As far as I know, this bug
exists on 3.9-rc1 too.
When I tried the latest mvebu for-next tree
On Tue, Mar 19, 2013 at 11:19:05PM +0900, Masami Hiramatsu wrote:
Hi Jason,
(2013/03/19 22:33), Jason Cooper wrote:
On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
Hi,
Here I've hit a bug on the recent kernel. As far as I know, this bug
exists on 3.9-rc1 too.
On 03/19/2013 03:19 PM, Masami Hiramatsu wrote:
Hi Ezequiel,
(2013/03/19 22:39), Ezequiel Garcia wrote:
Hi Masami,
On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
Here I've hit a bug on the recent kernel. As far as I know, this bug
exists on 3.9-rc1 too.
When I tried
On Tuesday 19 March 2013 17:43:49 Gregory CLEMENT wrote:
Hi Masami,
You can try this patch if you want.
I don't have the hardware today so I didn't test it.
If you (and also Florian and Ezequiel) can test it and if it fixed
the bug, then I will be able send a proper email for it,
I just
Hi Gregory,
On 03/19/2013 05:43 PM, Gregory CLEMENT wrote:
On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
Here I've hit a bug on the recent kernel. As far as I know, this bug
exists on 3.9-rc1 too.
When I tried the latest mvebu for-next tree
22 matches
Mail list logo
