From: Michal Simek <monstr@monstr.eu>
To: "Jens Renner (EFE)" <renner@efe-gmbh.de>
Cc: Michal Simek <michal.simek@xilinx.com>, netdev@vger.kernel.org
Subject: Re: [PATCH v2 0/6] Emaclite patches
Date: Fri, 31 May 2013 11:15:17 +0200 [thread overview]
Message-ID: <51A86A25.6070309@monstr.eu> (raw)
In-Reply-To: <51A868FF.5070903@efe-gmbh.de>
[-- Attachment #1: Type: text/plain, Size: 1927 bytes --]
On 05/31/2013 11:10 AM, Jens Renner (EFE) wrote:
> Am 30.05.2013 12:28, schrieb Michal Simek:
>> I have separated these emaclite patches from phy patches because it is
>> easier for creating new versions.
>>
>> Thanks, Michal
>>
>> Changes in v2: - Fix __raw_iowrite() to pass correct parameters -
>> s/Corrent/Correct/ in patch description
>>
>> Michal Simek (6): net: emaclite: Report failures in mdio setup net:
>> emaclite: Support multiple phys connected to one MDIO bus net: emaclite:
>> Let's make xemaclite_adjust_link static net: emaclite: Do not use
>> microblaze and ppc IO functions net: emaclite: Enable emaclite for Xilinx
>> Arm Zynq platform net: emaclite: Update driver header
>>
>> drivers/net/ethernet/xilinx/Kconfig | 4 +-
>> drivers/net/ethernet/xilinx/xilinx_emaclite.c | 169
>> ++++++++++++++------------ 2 files changed, 95 insertions(+), 78
>> deletions(-)
>
> Works without problems on our Microblaze platform (as far as the patches affect
> our functionality). MDIO verbosity has been tested ok.
>
>> @@ -862,8 +864,10 @@ static int xemaclite_mdio_setup(struct net_local *lp,
> struct device *dev)
>> XEL_MDIOCTRL_MDIOEN_MASK);
>>
>> bus = mdiobus_alloc(); - if (!bus) + if (!bus) { + dev_err(dev, "Failed to
>> allocal mdiobus\n"); return -ENOMEM; + }
>>
>> of_address_to_resource(np, 0, &res); snprintf(bus->id, MII_BUS_ID_SIZE,
>> "%.8llx",
>
> Shouldn't the wording be "allocate" instead of "allocal" in PATCH v2 1/6 (net:
> emaclite: Report failures in mdio setup)?
Ah yeah. Will you create patch to fix it?
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2013-05-31 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 10:28 [PATCH v2 0/6] Emaclite patches Michal Simek
2013-05-30 10:28 ` [PATCH v2 1/6] net: emaclite: Report failures in mdio setup Michal Simek
2013-05-30 10:28 ` [PATCH v2 2/6] net: emaclite: Support multiple phys connected to one MDIO bus Michal Simek
2013-05-30 10:28 ` [PATCH v2 3/6] net: emaclite: Let's make xemaclite_adjust_link static Michal Simek
2013-05-30 10:28 ` [PATCH v2 4/6] net: emaclite: Do not use microblaze and ppc IO functions Michal Simek
2013-05-30 10:28 ` [PATCH v2 5/6] net: emaclite: Enable emaclite for Xilinx Arm Zynq platform Michal Simek
2013-05-30 10:28 ` [PATCH v2 6/6] net: emaclite: Update driver header Michal Simek
2013-05-31 0:14 ` [PATCH v2 0/6] Emaclite patches David Miller
2013-05-31 9:10 ` Jens Renner (EFE)
2013-05-31 9:15 ` Michal Simek [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=51A86A25.6070309@monstr.eu \
--to=monstr@monstr.eu \
--cc=michal.simek@xilinx.com \
--cc=netdev@vger.kernel.org \
--cc=renner@efe-gmbh.de \
/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;
as well as URLs for NNTP newsgroup(s).