From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] ARM: shmobile: Koelsch: pass Ether PHY IRQ
Date: Mon, 06 Jan 2014 12:47:58 +0000 [thread overview]
Message-ID: <52CAA5FE.7020204@cogentembedded.com> (raw)
In-Reply-To: <20140106053915.GF24653@verge.net.au>
Hello.
On 06-01-2014 9:39, Simon Horman wrote:
>>>> Pass Ether's PHY IRQ (which is IRQC's IRQ0) to the 'sh_eth' driver. Set the IRQ
>>>> trigger type to be low-level as per the Micrel PHY driver's setup.
>>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>> Hi Sergei,
>>> does this depend on changes that have been queued up in net or net-next
>>> since v3.13-rc1?
>> Yes, in net-next.
>>> If so are they present in v3.13-rc5?
>> No, they should be available in 3.14-rc1.
>>> If not please
>>> repost when an rc release with the required dependencies is available.
>> You mean this patch should inevitably wait for 3.15? I hoped
>> either you or DaveM could still queue this patch for 3.14...
> Sorry, it was too late for v3.14 and I would prefer if you didn't route
> this via Dave's tree.
I somehow thought you were asking about the Lager patch. No, I wasn't
going to route the Koelsch patch via Dave, only Lager. Dave doesn't seem eager
to do it anyway.
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: shmobile: Koelsch: pass Ether PHY IRQ
Date: Mon, 06 Jan 2014 16:47:58 +0400 [thread overview]
Message-ID: <52CAA5FE.7020204@cogentembedded.com> (raw)
In-Reply-To: <20140106053915.GF24653@verge.net.au>
Hello.
On 06-01-2014 9:39, Simon Horman wrote:
>>>> Pass Ether's PHY IRQ (which is IRQC's IRQ0) to the 'sh_eth' driver. Set the IRQ
>>>> trigger type to be low-level as per the Micrel PHY driver's setup.
>>>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>>> Hi Sergei,
>>> does this depend on changes that have been queued up in net or net-next
>>> since v3.13-rc1?
>> Yes, in net-next.
>>> If so are they present in v3.13-rc5?
>> No, they should be available in 3.14-rc1.
>>> If not please
>>> repost when an rc release with the required dependencies is available.
>> You mean this patch should inevitably wait for 3.15? I hoped
>> either you or DaveM could still queue this patch for 3.14...
> Sorry, it was too late for v3.14 and I would prefer if you didn't route
> this via Dave's tree.
I somehow thought you were asking about the Lager patch. No, I wasn't
going to route the Koelsch patch via Dave, only Lager. Dave doesn't seem eager
to do it anyway.
WBR, Sergei
next prev parent reply other threads:[~2014-01-06 12:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 22:26 [PATCH 0/1] Add Ether's PHY IRQ support for R8A7791/Koelsch board Sergei Shtylyov
2013-12-19 23:26 ` Sergei Shtylyov
2013-12-19 22:27 ` [PATCH 1/1] ARM: shmobile: Koelsch: pass Ether PHY IRQ Sergei Shtylyov
2013-12-19 23:28 ` Sergei Shtylyov
2013-12-27 2:12 ` Simon Horman
2013-12-27 2:12 ` Simon Horman
2013-12-27 11:38 ` Sergei Shtylyov
2013-12-27 11:38 ` Sergei Shtylyov
2014-01-06 5:39 ` Simon Horman
2014-01-06 5:39 ` Simon Horman
2014-01-06 12:47 ` Sergei Shtylyov [this message]
2014-01-06 12:47 ` Sergei Shtylyov
2014-01-17 6:02 ` Magnus Damm
2014-01-17 6:02 ` Magnus Damm
2014-01-20 0:32 ` Simon Horman
2014-01-20 0:32 ` Simon Horman
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=52CAA5FE.7020204@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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.