From: David Miller <davem@redhat.com>
To: yegorslists@googlemail.com
Cc: netdev@vger.kernel.org, mugunthanvnm@ti.com
Subject: Re: [PATCH] net: cpsw: fix dual_emac VLAN issue
Date: Tue, 08 Apr 2014 14:15:28 -0400 (EDT) [thread overview]
Message-ID: <20140408.141528.2130884658575478739.davem@redhat.com> (raw)
In-Reply-To: <1396969110-3114-2-git-send-email-yegorslists@googlemail.com>
From: yegorslists@googlemail.com
Date: Tue, 8 Apr 2014 16:58:30 +0200
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> CPSW shows following behavior: some stations in LAN don't
> answer CPSW's ARP request. Kernel 3.2 could talk to all stations in
> the same LAN.
>
> Use the same cpsw_ale_add_vlan procedure as in kernel 3.2.
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
The CPSW driver was not added to the tree until v3.3, so saying
you're restoring behavior that existed in v3.2 doesn't make any
sense at all.
next prev parent reply other threads:[~2014-04-08 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 14:58 CPSW: dual_emac issue (D-01525) yegorslists
2014-04-08 14:58 ` [PATCH] net: cpsw: fix dual_emac VLAN issue yegorslists
2014-04-08 18:15 ` David Miller [this message]
2014-04-08 18:57 ` Yegor Yefremov
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=20140408.141528.2130884658575478739.davem@redhat.com \
--to=davem@redhat.com \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=yegorslists@googlemail.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).