LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Esben Haabendal <esben@geanix.com> To: netdev@vger.kernel.org Cc: "David S. Miller" <davem@davemloft.net>, Michal Simek <michal.simek@xilinx.com>, Andrew Lunn <andrew@lunn.ch>, YueHaibing <yuehaibing@huawei.com>, Dan Carpenter <dan.carpenter@oracle.com>, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/4] net: ll_temac: Fix and enable multicast support Date: Thu, 23 May 2019 14:02:18 +0200 [thread overview] Message-ID: <20190523120222.3807-1-esben@geanix.com> (raw) This patch series makes the necessary fixes to ll_temac driver to make multicast work, and enables support for it.so that multicast support can The main change is the change from mutex to spinlock of the lock used to synchronize access to the shared indirect register access. Esben Haabendal (4): net: ll_temac: Do not make promiscuous mode sticky on multicast net: ll_temac: Prepare indirect register access for multicast support net: ll_temac: Cleanup multicast filter on change net: ll_temac: Enable multicast support drivers/net/ethernet/xilinx/ll_temac.h | 5 +- drivers/net/ethernet/xilinx/ll_temac_main.c | 255 +++++++++++++++++--------- drivers/net/ethernet/xilinx/ll_temac_mdio.c | 20 +- include/linux/platform_data/xilinx-ll-temac.h | 3 +- 4 files changed, 184 insertions(+), 99 deletions(-) -- 2.4.11
next reply other threads:[~2019-05-23 12:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-23 12:02 Esben Haabendal [this message] 2019-05-23 12:02 ` [PATCH 1/4] net: ll_temac: Do not make promiscuous mode sticky on multicast Esben Haabendal 2019-05-23 12:02 ` [PATCH 2/4] net: ll_temac: Prepare indirect register access for multicast support Esben Haabendal 2019-05-23 12:02 ` [PATCH 3/4] net: ll_temac: Cleanup multicast filter on change Esben Haabendal 2019-05-23 12:02 ` [PATCH 4/4] net: ll_temac: Enable multicast support Esben Haabendal 2019-05-23 16:34 ` [PATCH 0/4] net: ll_temac: Fix and enable " David Miller
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=20190523120222.3807-1-esben@geanix.com \ --to=esben@geanix.com \ --cc=andrew@lunn.ch \ --cc=dan.carpenter@oracle.com \ --cc=davem@davemloft.net \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=michal.simek@xilinx.com \ --cc=netdev@vger.kernel.org \ --cc=yuehaibing@huawei.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: linkBe 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).