From: David Miller <davem@davemloft.net>
To: boris.brezillon@free-electrons.com
Cc: netdev@vger.kernel.org, nicolas.ferre@atmel.com,
plagnioj@jcrosoft.com, alexandre.belloni@free-electrons.com,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] net/macb: merge at91_ether driver into macb driver
Date: Fri, 06 Mar 2015 15:16:53 -0500 (EST) [thread overview]
Message-ID: <20150306.151653.2133726487330517804.davem@davemloft.net> (raw)
In-Reply-To: <1425622439-2372-1-git-send-email-boris.brezillon@free-electrons.com>
From: Boris Brezillon <boris.brezillon@free-electrons.com>
Date: Fri, 6 Mar 2015 07:13:57 +0100
> The rm9200 boards use the dedicated at91_ether driver instead of the
> regular macb driver.
>
> Both the macb and at91_ether drivers can be compiled as separated
> modules.
> Since the at91_ether driver uses code from the macb driver, at91_ether.ko
> depends on macb.ko.
>
> However the macb.ko module always fails to load on rm9200 boards: the
> macb_probe() function expects a hclk clock which doesn't exist on rm9200.
> Then the at91_ether.ko can't be loaded in turn due to unresolved
> dependencies.
>
> This series of patches fix this issue by merging at91_ether into macb.
Series applied to net-next, thanks.
prev parent reply other threads:[~2015-03-06 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 6:13 Boris Brezillon
2015-03-06 6:13 ` [PATCH v2 1/2] net/macb: unify clock management Boris Brezillon
2015-03-06 6:13 ` [PATCH v2 2/2] net/macb: merge at91_ether driver into macb driver Boris Brezillon
2015-03-06 8:17 ` Alexandre Belloni
2015-03-06 8:11 ` [PATCH v2 1/2] net/macb: unify clock management Boris Brezillon
2015-03-06 20:16 ` David Miller [this message]
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=20150306.151653.2133726487330517804.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=pawel.moll@arm.com \
--cc=plagnioj@jcrosoft.com \
--cc=robh+dt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®