From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: David Miller <davem@davemloft.net>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
netdev@vger.kernel.org, nsekhar@ti.com,
open list <linux-kernel@vger.kernel.org>,
linux-omap@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] net: ethernet: ti: cpsw: fix packet leaking in dual_mac mode
Date: Thu, 17 May 2018 23:18:16 +0530 [thread overview]
Message-ID: <CA+G9fYv5yXD4_hyUSxWra+gxux1NFv+sD2HgB7LyJ4E78bgh+A@mail.gmail.com> (raw)
In-Reply-To: <20180502.110841.378324128079268584.davem@davemloft.net>
On 2 May 2018 at 20:38, David Miller <davem@davemloft.net> wrote:
> From: Grygorii Strashko <grygorii.strashko@ti.com>
> Date: Tue, 1 May 2018 12:41:22 -0500
<trim>
>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>
> Applied and queued up for -stable, thank you.
4.4 stable-rc build failed for arm32.
MACHINE=am57xx-evm
Build error log:
--------------------
drivers/net/ethernet/ti/cpsw.c:
In function 'cpsw_add_dual_emac_def_ale_entries':
drivers/net/ethernet/ti/cpsw.c:1112:23:
error: 'cpsw' undeclared (first use in this function)
cpsw_ale_control_set(cpsw->ale, slave_port,
^~~~
drivers/net/ethernet/ti/cpsw.c:1112:23: note:
each undeclared identifier is reported only once for each function it appears
in
scripts/Makefile.build:269: recipe for target 'drivers/net/ethernet/ti/cpsw.o'
failed
make[6]: *** [drivers/net/ethernet/ti/cpsw.o] Error 1
scripts/Makefile.build:476: recipe for target 'drivers/net/ethernet/ti' failed
make[5]: *** [drivers/net/ethernet/ti] Error 2
Complete log link:
https://ci.linaro.org/job/openembedded-lkft-linux-stable-rc-4.4/DISTRO=rpb,MACHINE=am57xx-evm,label=docker-lkft/205/console
next prev parent reply other threads:[~2018-05-17 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 17:41 [PATCH] net: ethernet: ti: cpsw: fix packet leaking in dual_mac mode Grygorii Strashko
2018-05-02 15:08 ` David Miller
2018-05-17 17:48 ` Naresh Kamboju [this message]
2018-05-17 19:10 ` Greg Kroah-Hartman
2018-05-18 16:37 ` Grygorii Strashko
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=CA+G9fYv5yXD4_hyUSxWra+gxux1NFv+sD2HgB7LyJ4E78bgh+A@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
/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).