From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Andrew Lunn <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
adi-buildroot-devel@lists.sourceforge.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next 1/2] net: bfin_mac: Fix error handling in probe function
Date: Mon, 11 Jan 2016 14:13:51 +0530 [thread overview]
Message-ID: <20160111084350.GC8070@sudip-pc> (raw)
In-Reply-To: <569275C0.1040606@roeck-us.net>
On Sun, Jan 10, 2016 at 07:16:16AM -0800, Guenter Roeck wrote:
> On 01/09/2016 12:52 PM, Andrew Lunn wrote:
> >On Sat, Jan 09, 2016 at 10:10:41AM -0800, Guenter Roeck wrote:
> >>Hi Andrew,
> >>
> >>On 01/09/2016 08:58 AM, Andrew Lunn wrote:
> >>>Hi Guenter
> >>>
> >>>Same fix was submitted yesterday by Sudip Mukherjee.
> >>>
> >>
> >>I missed that one, sorry.
> >>
> >>How about drivers/net/ethernet/toshiba/tc35815.c ? It now has an unused
> >>variable due to e7f4dc3536a4, and it fails to build because of 7f854420fbfe.
> >>
> >>Which leads to the question which of the other build failures due to
> >>7f854420fbfe have been addressed already. In addition to the toshiba driver,
> >>I see build failures in drivers/net/ethernet/ti/cpmac.c and possibly
> >>drivers/staging/octeon/ethernet-rgmii.c (the error message is different,
> >>so it may be something else).
> >>
> >>I don't see patches for those, but I guess I must be blind, so I figure I
> >>better ask before I send out mine.
> >
> >That i have seen so far:
> >
> >Wantiq_etp.c: Me
> >octeon/ethernet-rgmii.c: Me
> >adi/bfin_mac.c: Sudip Mukerjee
>
> I re-posted this one anyway, using phy_find_first.
>
> >nxp/lpc_eth.c: Fabio Estevam
> >
> >Plus there is an interesting one for micrel.c which is going to have
> >to wait a while.
> >
> How about those ?
>
> drivers/net/ethernet/freescale/ucc_geth.c: In function 'uec_configure_serdes':
> drivers/net/ethernet/freescale/ucc_geth.c:1719:20: error: 'struct phy_device' has no member named 'dev'
>
> drivers/net/ethernet/freescale/fs_enet/mac-fec.c: In function 'stop':
> drivers/net/ethernet/freescale/fs_enet/mac-fec.c:366:36: error: 'struct phy_device' has no member named 'bus'
My builds didn't show them not even the other ones mentioned above. :(
Which config you used for these?
regards
sudip
next prev parent reply other threads:[~2016-01-11 8:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 16:37 [PATCH -next 1/2] net: bfin_mac: Fix error handling in probe function Guenter Roeck
2016-01-09 16:37 ` [PATCH -next 2/2] net: bfin_mac: Fix build error due to missed API change Guenter Roeck
2016-01-09 16:58 ` [PATCH -next 1/2] net: bfin_mac: Fix error handling in probe function Andrew Lunn
2016-01-09 18:10 ` Guenter Roeck
2016-01-09 20:52 ` Andrew Lunn
2016-01-10 15:16 ` Guenter Roeck
2016-01-10 15:49 ` Andrew Lunn
2016-01-10 16:22 ` Guenter Roeck
2016-01-10 17:21 ` Andrew Lunn
2016-01-10 20:10 ` Guenter Roeck
2016-01-10 23:58 ` Andrew Lunn
2016-01-11 8:43 ` Sudip Mukherjee [this message]
2016-01-11 16:23 ` Guenter Roeck
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=20160111084350.GC8070@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).