From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Stefan Chulski <stefanc@marvell.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>,
"davem@davemloft.net" <davem@davemloft.net>,
Nadav Haklai <nadavh@marvell.com>,
Yan Markman <ymarkman@marvell.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mw@semihalf.com" <mw@semihalf.com>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"atenart@kernel.org" <atenart@kernel.org>
Subject: Re: [EXT] Re: [PATCH v5 net-next 00/18] net: mvpp2: Add TX Flow Control support
Date: Sun, 31 Jan 2021 15:00:25 +0000 [thread overview]
Message-ID: <20210131150025.GB1477@shell.armlinux.org.uk> (raw)
In-Reply-To: <20210131144524.GD1463@shell.armlinux.org.uk>
On Sun, Jan 31, 2021 at 02:45:24PM +0000, Russell King - ARM Linux admin wrote:
> On Sun, Jan 31, 2021 at 02:23:20PM +0000, Stefan Chulski wrote:
> > I still don't see all patches in https://patchwork.kernel.org/project/netdevbpf/list/?series=424949
> > I would reduce patch series to 15 patches and repost again.
>
> kernel.org email is currently broken for everyone due to the
> spamcop.net RBL domain having expired. Please don't resend until
> this has been resolved. The problem has been reported to a
> kernel.org admin (John Hawley) and others via IRC.
>
> If you didn't get bounce messages from the attempt to send to
> kernel.org email addresses, your email server is broken.
Ok, kernel.org has now dropped spamcop.net, so email should flow
normally now.
Are you sure all your emails are being received by vger.kernel.org?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2021-01-31 15:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1611858682-9845-1-git-send-email-stefanc@marvell.com>
2021-01-28 18:31 ` [PATCH v5 net-next 04/18] doc: marvell: add PPv2.3 description to marvell-pp2.txt stefanc
2021-01-28 18:31 ` [PATCH v5 net-next 06/18] net: mvpp2: always compare hw-version vs MVPP21 stefanc
2021-01-28 18:31 ` [PATCH v5 net-next 08/18] net: mvpp2: increase RXQ size to 1024 descriptors stefanc
2021-01-28 18:31 ` [PATCH v5 net-next 09/18] net: mvpp2: add FCA periodic timer configurations stefanc
2021-01-28 18:31 ` [PATCH v5 net-next 10/18] net: mvpp2: add FCA RXQ non occupied descriptor threshold stefanc
2021-01-28 18:31 ` [PATCH v5 net-next 11/18] net: mvpp2: enable global flow control stefanc
2021-01-28 18:31 ` [PATCH v5 net-next 12/18] net: mvpp2: add RXQ flow control configurations stefanc
2021-01-28 18:31 ` [PATCH v5 net-next 13/18] net: mvpp2: add ethtool flow control configuration support stefanc
2021-01-28 18:31 ` [PATCH v5 net-next 14/18] net: mvpp2: add BM protection underrun feature support stefanc
2021-01-28 18:31 ` [PATCH v5 net-next 15/18] net: mvpp2: add PPv23 RX FIFO flow control stefanc
2021-01-28 18:31 ` [PATCH v5 net-next 16/18] net: mvpp2: set 802.3x GoP Flow Control mode stefanc
2021-01-28 18:31 ` [PATCH v5 net-next 17/18] net: mvpp2: limit minimum ring size to 1024 descriptors stefanc
2021-01-28 18:31 ` [PATCH v5 net-next 18/18] net: mvpp2: add TX FC firmware check stefanc
2021-01-29 2:20 ` [PATCH v5 net-next 00/18] net: mvpp2: Add TX Flow Control support Jakub Kicinski
[not found] ` <CO6PR18MB38736602343EEDFB934ACE3EB0B79@CO6PR18MB3873.namprd18.prod.outlook.com>
[not found] ` <CO6PR18MB3873FF66600BCD9E7E5A4FEDB0B79@CO6PR18MB3873.namprd18.prod.outlook.com>
[not found] ` <20210131144524.GD1463@shell.armlinux.org.uk>
2021-01-31 15:00 ` Russell King - ARM Linux admin [this message]
2021-01-31 15:10 ` [EXT] " Stefan Chulski
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=20210131150025.GB1477@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=stefanc@marvell.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=ymarkman@marvell.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).