From: masami.hiramatsu.pt@hitachi.com (Masami Hiramatsu)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG][mvebu] mvneta: cannot request irq 25 on openblocks-ax3
Date: Tue, 19 Mar 2013 23:19:05 +0900 [thread overview]
Message-ID: <514873D9.6060704@hitachi.com> (raw)
In-Reply-To: <20130319133324.GS13280@titan.lakedaemon.net>
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
>> (git://git.infradead.org/users/jcooper/linux.git mvebu/for-next),
>
> FYI: that branch isn't stable, it's used as a merge-test of
> arm-soc/for-next (also not stable) and any branches I am trying to push
> upstream that day.
Thanks! could you tell me which branch is stable?
(however, I'd like to try new fixes/features on my device too :))
> Gregory has a patch in the works for this. Hopefully he'll submit
> it by the end of the week.
Thank you,
--
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt at hitachi.com
WARNING: multiple messages have this Message-ID (diff)
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: linux-arm-kernel@lists.infradead.org,
thomas.petazzoni@free-electrons.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
"yrl.pp-manager.tt@hitachi.com" <yrl.pp-manager.tt@hitachi.com>
Subject: Re: Re: [BUG][mvebu] mvneta: cannot request irq 25 on openblocks-ax3
Date: Tue, 19 Mar 2013 23:19:05 +0900 [thread overview]
Message-ID: <514873D9.6060704@hitachi.com> (raw)
In-Reply-To: <20130319133324.GS13280@titan.lakedaemon.net>
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
>> (git://git.infradead.org/users/jcooper/linux.git mvebu/for-next),
>
> FYI: that branch isn't stable, it's used as a merge-test of
> arm-soc/for-next (also not stable) and any branches I am trying to push
> upstream that day.
Thanks! could you tell me which branch is stable?
(however, I'd like to try new fixes/features on my device too :))
> Gregory has a patch in the works for this. Hopefully he'll submit
> it by the end of the week.
Thank you,
--
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2013-03-19 14:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 13:12 [BUG][mvebu] mvneta: cannot request irq 25 on openblocks-ax3 Masami Hiramatsu
2013-03-19 13:12 ` Masami Hiramatsu
2013-03-19 13:33 ` Jason Cooper
2013-03-19 13:33 ` Jason Cooper
2013-03-19 14:19 ` Masami Hiramatsu [this message]
2013-03-19 14:19 ` Masami Hiramatsu
2013-03-19 14:33 ` Jason Cooper
2013-03-19 14:33 ` Jason Cooper
2013-03-19 13:39 ` Ezequiel Garcia
2013-03-19 13:39 ` Ezequiel Garcia
2013-03-19 14:19 ` Masami Hiramatsu
2013-03-19 14:19 ` Masami Hiramatsu
2013-03-19 16:43 ` Gregory CLEMENT
2013-03-19 16:43 ` Gregory CLEMENT
2013-03-19 19:48 ` Florian Fainelli
2013-03-19 19:48 ` Florian Fainelli
2013-03-20 15:09 ` Gregory CLEMENT
2013-03-20 15:09 ` Gregory CLEMENT
2013-03-21 1:56 ` Masami Hiramatsu
2013-03-21 1:56 ` Masami Hiramatsu
[not found] <CABx3TkU7e9ZUDYhegUBD+XbG03+Q+dxF8jzeUe4Cao9Hg_TpBw@mail.gmail.com>
2013-03-20 2:11 ` Ryan Press
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=514873D9.6060704@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.