All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Granados <j.granados@samsung.com>
To: Chris Maness <christopher.maness@gmail.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	Alexander Aring <alex.aring@gmail.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	"D. Wythe" <alibuda@linux.alibaba.com>,
	David Ahern <dsahern@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Florian Westphal <fw@strlen.de>,
	Heiko Carstens <hca@linux.ibm.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Iurii Zaikin <yzaikin@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Jan Karcher <jaka@linux.ibm.com>, Joerg Reuter <jreuter@yaina.de>,
	Jozsef Kadlecsik <kadlec@netfilter.org>,
	Julian Anastasov <ja@ssi.bg>,
	Karsten Graul <kgraul@linux.ibm.com>,
	Kees Cook <keescook@chromium.org>,
	Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	Mat Martineau <martineau@kernel.org>,
	Matthieu Baerts <matthieu.baerts@tessares.net>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Nikolay Aleksandrov <razor@blackwall.org>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	Paolo Abeni <pabeni@redhat.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Roopa Prabhu <roopa@nvidia.com>,
	Santosh Shilimkar <santosh.shilimkar@oracle.com>,
	Simon Horman <horms@verge.net.au>,
	Stefan Schmidt <stefan@datenfreihafen.org>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	Tony Lu <tonylu@linux.alibaba.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Wen Gu <guwen@linux.alibaba.com>,
	Wenjia Zhang <wenjia@linux.ibm.com>,
	Will Deacon <will@kernel.org>, Xin Long <lucien.xin@gmail.com>,
	<bridge@lists.linux-foundation.org>, <coreteam@netfilter.org>,
	<josh@joshtriplett.org>, <linux-arm-kernel@lists.infradead.org>,
	<linux-fsdevel@vger.kernel.org>, <linux-hams@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
	<linux-s390@vger.kernel.org>, <linux-sctp@vger.kernel.org>,
	<linux-wpan@vger.kernel.org>, <lvs-devel@vger.kernel.org>,
	<mptcp@lists.linux.dev>, <netdev@vger.kernel.org>,
	<netfilter-devel@vger.kernel.org>, <rds-devel@oss.oracle.com>,
	<willy@infradead.org>
Subject: Re: [PATCH v2 00/14] sysctl: Add a size argument to register functions in sysctl
Date: Tue, 8 Aug 2023 15:58:47 +0200	[thread overview]
Message-ID: <20230808135847.46ln434mbpiiklvz@localhost> (raw)
In-Reply-To: <CANnsUMGRBnatKB4-3eYjb5aG7YnXDiZG6cjuwSgtjvVF6ErJNg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]

Hey Chris

My questions inline
On Mon, Aug 07, 2023 at 07:50:44PM -0700, Chris Maness wrote:
> I tried running the current mainline kernel (current Arch Linux) with
What kernel version are we talking about exactly here? Please notice the
base that I used in the cover letter (rc2 or rc3). They should also
rebase cleanly on top of v6.5-rc5.

I'm not sure what the patches will do if you apply them to an older
kernel.

> simple single MUX socket (ax0) using LinFBB.  I was a happy camper as
> it seemed to work fine at first, then the system just slowed to a
> crawl.  I am wondering if any of these patches are addressing this
> behavior.  No kernel panic like before, but not what I was hoping for.
So you have been experiencing kernel panics from before? What does
before mean? And can you bisect to pinpoint what commit fixed it?

> I have also tried sixpack, and that explodes instantly the last time I
> have checked.   That goes all the way back to the v4 kernels.  v2 is
> fine there.
You mean that 6pack is broken in all the major versions up until v2? If
this is the case, then it might be an issue that is not related to this
patchset.I see that Andreas Koensgen <ajk@comnets.uni-bremen.de> is the
maintainer of 6pack, maybe he can chime in on the issue?

> 
> 73 de Chris KQ6UP
> 
> On Mon, Aug 7, 2023 at 4:43 PM Luis Chamberlain <mcgrof@kernel.org> wrote:
> >
> > On Mon, Aug 07, 2023 at 04:00:49PM -0700, Chris Maness wrote:
> > > When are these likely to hit the mainline release code?
> >
> > linux-next tomorrow. The first 7 patches are scheduled for mainline
> > as they were merged + tested without any hiccups. These last few patches
> > I'll wait and see. If nothing blows up on linux-next perhaps I'll
> > include them to Linux for mainline during the next merge window.
> >
> >   Luis
> 
> 
> 
> -- 
> Thanks,
> Chris Maness

-- 

Joel Granados

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Joel Granados <j.granados@samsung.com>
To: Chris Maness <christopher.maness@gmail.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	Alexander Aring <alex.aring@gmail.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	"D. Wythe" <alibuda@linux.alibaba.com>,
	David Ahern <dsahern@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Florian Westphal <fw@strlen.de>,
	Heiko Carstens <hca@linux.ibm.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Iurii Zaikin <yzaikin@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Jan Karcher <jaka@linux.ibm.com>, Joerg Reuter <jreuter@yaina.de>,
	Jozsef Kadlecsik <kadlec@netfilter.org>,
	Julian Anastasov <ja@ssi.bg>,
	Karsten Graul <kgraul@linux.ibm.com>, Kees Cook <keescook@c>
Subject: Re: [PATCH v2 00/14] sysctl: Add a size argument to register functions in sysctl
Date: Tue, 8 Aug 2023 15:58:47 +0200	[thread overview]
Message-ID: <20230808135847.46ln434mbpiiklvz@localhost> (raw)
In-Reply-To: <CANnsUMGRBnatKB4-3eYjb5aG7YnXDiZG6cjuwSgtjvVF6ErJNg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]

Hey Chris

My questions inline
On Mon, Aug 07, 2023 at 07:50:44PM -0700, Chris Maness wrote:
> I tried running the current mainline kernel (current Arch Linux) with
What kernel version are we talking about exactly here? Please notice the
base that I used in the cover letter (rc2 or rc3). They should also
rebase cleanly on top of v6.5-rc5.

I'm not sure what the patches will do if you apply them to an older
kernel.

> simple single MUX socket (ax0) using LinFBB.  I was a happy camper as
> it seemed to work fine at first, then the system just slowed to a
> crawl.  I am wondering if any of these patches are addressing this
> behavior.  No kernel panic like before, but not what I was hoping for.
So you have been experiencing kernel panics from before? What does
before mean? And can you bisect to pinpoint what commit fixed it?

> I have also tried sixpack, and that explodes instantly the last time I
> have checked.   That goes all the way back to the v4 kernels.  v2 is
> fine there.
You mean that 6pack is broken in all the major versions up until v2? If
this is the case, then it might be an issue that is not related to this
patchset.I see that Andreas Koensgen <ajk@comnets.uni-bremen.de> is the
maintainer of 6pack, maybe he can chime in on the issue?

> 
> 73 de Chris KQ6UP
> 
> On Mon, Aug 7, 2023 at 4:43 PM Luis Chamberlain <mcgrof@kernel.org> wrote:
> >
> > On Mon, Aug 07, 2023 at 04:00:49PM -0700, Chris Maness wrote:
> > > When are these likely to hit the mainline release code?
> >
> > linux-next tomorrow. The first 7 patches are scheduled for mainline
> > as they were merged + tested without any hiccups. These last few patches
> > I'll wait and see. If nothing blows up on linux-next perhaps I'll
> > include them to Linux for mainline during the next merge window.
> >
> >   Luis
> 
> 
> 
> -- 
> Thanks,
> Chris Maness

-- 

Joel Granados

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Joel Granados <j.granados@samsung.com>
To: Chris Maness <christopher.maness@gmail.com>
Cc: Alexander Aring <alex.aring@gmail.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Nikolay Aleksandrov <razor@blackwall.org>,
	Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	netfilter-devel@vger.kernel.org,
	Eric Dumazet <edumazet@google.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Paolo Abeni <pabeni@redhat.com>, Jan Karcher <jaka@linux.ibm.com>,
	Jozsef Kadlecsik <kadlec@netfilter.org>,
	Tony Lu <tonylu@linux.alibaba.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Stefan Schmidt <stefan@datenfreihafen.org>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	linux-s390@vger.kernel.org, rds-devel@oss.oracle.com,
	Xin Long <lucien.xin@gmail.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	linux-rdma@vger.kernel.org, Will Deacon <will@kernel.org>,
	bridge@lists.linux-foundation.org, willy@infradead.org,
	Mat Martineau <martineau@kernel.org>,
	lvs-devel@vger.kernel.org, Julian Anastasov <ja@ssi.bg>,
	coreteam@netfilter.org, Roopa Prabhu <roopa@nvidia.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Iurii Zaikin <yzaikin@google.com>,
	Joerg Reuter <jreuter@yaina.de>,
	Sven Schnelle <svens@linux.ibm.com>,
	Kees Cook <keescook@chromium.org>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Santosh Shilimkar <santosh.shilimkar@oracle.com>,
	linux-sctp@vger.kernel.org, josh@joshtriplett.org,
	Wenjia Zhang <wenjia@linux.ibm.com>,
	Simon Horman <horms@verge.net.au>,
	linux-hams@vger.kernel.org, mptcp@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	netdev@vger.kernel.org, David Ahern <dsahern@kernel.org>,
	Florian Westphal <fw@strlen.de>,
	linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>,
	"David S. Miller" <davem@davemloft.net>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Wen Gu <guwen@linux.alibaba.com>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	"D. Wythe" <alibuda@linux.alibaba.com>,
	linux-fsdevel@vger.kernel.org,
	Matthieu Baerts <matthieu.baerts@tessares.net>,
	linux-wpan@vger.kernel.org, Karsten Graul <kgraul@linux.ibm.com>
Subject: Re: [Bridge] [PATCH v2 00/14] sysctl: Add a size argument to register functions in sysctl
Date: Tue, 8 Aug 2023 15:58:47 +0200	[thread overview]
Message-ID: <20230808135847.46ln434mbpiiklvz@localhost> (raw)
In-Reply-To: <CANnsUMGRBnatKB4-3eYjb5aG7YnXDiZG6cjuwSgtjvVF6ErJNg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]

Hey Chris

My questions inline
On Mon, Aug 07, 2023 at 07:50:44PM -0700, Chris Maness wrote:
> I tried running the current mainline kernel (current Arch Linux) with
What kernel version are we talking about exactly here? Please notice the
base that I used in the cover letter (rc2 or rc3). They should also
rebase cleanly on top of v6.5-rc5.

I'm not sure what the patches will do if you apply them to an older
kernel.

> simple single MUX socket (ax0) using LinFBB.  I was a happy camper as
> it seemed to work fine at first, then the system just slowed to a
> crawl.  I am wondering if any of these patches are addressing this
> behavior.  No kernel panic like before, but not what I was hoping for.
So you have been experiencing kernel panics from before? What does
before mean? And can you bisect to pinpoint what commit fixed it?

> I have also tried sixpack, and that explodes instantly the last time I
> have checked.   That goes all the way back to the v4 kernels.  v2 is
> fine there.
You mean that 6pack is broken in all the major versions up until v2? If
this is the case, then it might be an issue that is not related to this
patchset.I see that Andreas Koensgen <ajk@comnets.uni-bremen.de> is the
maintainer of 6pack, maybe he can chime in on the issue?

> 
> 73 de Chris KQ6UP
> 
> On Mon, Aug 7, 2023 at 4:43 PM Luis Chamberlain <mcgrof@kernel.org> wrote:
> >
> > On Mon, Aug 07, 2023 at 04:00:49PM -0700, Chris Maness wrote:
> > > When are these likely to hit the mainline release code?
> >
> > linux-next tomorrow. The first 7 patches are scheduled for mainline
> > as they were merged + tested without any hiccups. These last few patches
> > I'll wait and see. If nothing blows up on linux-next perhaps I'll
> > include them to Linux for mainline during the next merge window.
> >
> >   Luis
> 
> 
> 
> -- 
> Thanks,
> Chris Maness

-- 

Joel Granados

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  parent reply	other threads:[~2023-08-09  7:13 UTC|newest]

Thread overview: 107+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31  7:17 [PATCH v2 00/14] sysctl: Add a size argument to register functions in sysctl Joel Granados
2023-07-31  7:17 ` [Bridge] " Joel Granados
2023-07-31  7:17 ` Joel Granados
2023-07-31  7:17 ` [PATCH v2 01/14] sysctl: Prefer ctl_table_header in proc_sysctl Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-07-31  7:17 ` [PATCH v2 02/14] sysctl: Use ctl_table_header in list_for_each_table_entry Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-07-31  7:17 ` [PATCH v2 03/14] sysctl: Add ctl_table_size to ctl_table_header Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-07-31 18:30   ` Simon Horman
2023-07-31 18:30     ` [Bridge] " Simon Horman
2023-07-31 18:30     ` Simon Horman
2023-07-31 19:07     ` Simon Horman
2023-07-31 19:07       ` [Bridge] " Simon Horman
2023-07-31 19:07       ` Simon Horman
2023-08-01 10:03       ` Joel Granados
2023-08-01 10:03         ` [Bridge] " Joel Granados
2023-08-01 10:03         ` Joel Granados
2023-07-31  7:17 ` [PATCH v2 04/14] sysctl: Add size argument to init_header Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-07-31  7:17 ` [PATCH v2 05/14] sysctl: Add a size arg to __register_sysctl_table Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-07-31  7:17 ` [PATCH v2 06/14] sysctl: Add size to register_sysctl Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-07-31  7:17 ` [PATCH v2 07/14] sysctl: Add size arg to __register_sysctl_init Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-07-31  7:17 ` [PATCH v2 08/14] sysctl: Add size to register_net_sysctl function Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-07-31  7:17 ` [PATCH v2 09/14] ax.25: Update to register_net_sysctl_sz Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-07-31  7:17 ` [PATCH v2 10/14] netfilter: " Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-08-01  6:11   ` Julian Anastasov
2023-08-01  6:11     ` [Bridge] " Julian Anastasov
2023-08-01  6:11     ` Julian Anastasov
2023-07-31  7:17 ` [PATCH v2 11/14] networking: " Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-08-08 11:20   ` Przemek Kitszel
2023-08-08 11:20     ` [Bridge] " Przemek Kitszel
2023-08-08 11:20     ` Przemek Kitszel
2023-08-08 14:24     ` Joel Granados
2023-08-08 14:24       ` [Bridge] " Joel Granados
2023-08-08 14:24       ` Joel Granados
2023-08-08 15:23     ` Joel Granados
2023-08-08 15:23       ` [Bridge] " Joel Granados
2023-08-08 15:23       ` Joel Granados
2023-07-31  7:17 ` [PATCH v2 12/14] vrf: " Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-07-31  7:17 ` [PATCH v2 13/14] sysctl: SIZE_MAX->ARRAY_SIZE in register_net_sysctl Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-07-31  7:17 ` [PATCH v2 14/14] sysctl: Use ctl_table_size as stopping criteria for list macro Joel Granados
2023-07-31  7:17   ` [Bridge] " Joel Granados
2023-07-31  7:17   ` Joel Granados
2023-07-31 20:50 ` [PATCH v2 00/14] sysctl: Add a size argument to register functions in sysctl Luis Chamberlain
2023-07-31 20:50   ` [Bridge] " Luis Chamberlain
2023-07-31 20:50   ` Luis Chamberlain
2023-08-01 10:01   ` Joel Granados
2023-08-01 10:01     ` [Bridge] " Joel Granados
2023-08-01 10:01     ` Joel Granados
2023-07-31 21:36 ` Luis Chamberlain
2023-07-31 21:36   ` [Bridge] " Luis Chamberlain
2023-07-31 21:36   ` Luis Chamberlain
2023-08-01  9:35   ` Joel Granados
2023-08-01  9:35     ` [Bridge] " Joel Granados
2023-08-01  9:35     ` Joel Granados
2023-08-07 21:44   ` Luis Chamberlain
2023-08-07 21:44     ` [Bridge] " Luis Chamberlain
2023-08-07 21:44     ` Luis Chamberlain
2023-08-07 23:00     ` Chris Maness
2023-08-07 23:00       ` [Bridge] " Chris Maness
2023-08-07 23:43       ` Luis Chamberlain
2023-08-07 23:43         ` [Bridge] " Luis Chamberlain
2023-08-07 23:43         ` Luis Chamberlain
2023-08-08  2:50         ` Chris Maness
2023-08-08  2:50           ` [Bridge] " Chris Maness
2023-08-08  2:50           ` Chris Maness
2023-08-08  3:00           ` Luis Chamberlain
2023-08-08  3:00             ` [Bridge] " Luis Chamberlain
2023-08-08  3:00             ` Luis Chamberlain
2023-08-08  3:07             ` Chris Maness
2023-08-08  3:07               ` [Bridge] " Chris Maness
2023-08-08  3:07               ` Chris Maness
2023-08-08 13:59               ` Joel Granados
2023-08-08 13:59                 ` [Bridge] " Joel Granados
2023-08-08 13:59                 ` Joel Granados
2023-08-08 13:58           ` Joel Granados [this message]
2023-08-08 13:58             ` [Bridge] " Joel Granados
2023-08-08 13:58             ` Joel Granados
2023-08-08  2:09     ` Jakub Kicinski
2023-08-08  2:09       ` [Bridge] " Jakub Kicinski
2023-08-08  2:09       ` Jakub Kicinski
2023-08-08  2:34       ` Luis Chamberlain
2023-08-08  2:34         ` [Bridge] " Luis Chamberlain
2023-08-08  2:34         ` Luis Chamberlain

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=20230808135847.46ln434mbpiiklvz@localhost \
    --to=j.granados@samsung.com \
    --cc=agordeev@linux.ibm.com \
    --cc=alex.aring@gmail.com \
    --cc=alibuda@linux.alibaba.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=christopher.maness@gmail.com \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=gor@linux.ibm.com \
    --cc=guwen@linux.alibaba.com \
    --cc=hca@linux.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=jaka@linux.ibm.com \
    --cc=josh@joshtriplett.org \
    --cc=jreuter@yaina.de \
    --cc=kadlec@netfilter.org \
    --cc=keescook@chromium.org \
    --cc=kgraul@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=lvs-devel@vger.kernel.org \
    --cc=marcelo.leitner@gmail.com \
    --cc=martineau@kernel.org \
    --cc=matthieu.baerts@tessares.net \
    --cc=mcgrof@kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pablo@netfilter.org \
    --cc=ralf@linux-mips.org \
    --cc=razor@blackwall.org \
    --cc=rds-devel@oss.oracle.com \
    --cc=roopa@nvidia.com \
    --cc=santosh.shilimkar@oracle.com \
    --cc=stefan@datenfreihafen.org \
    --cc=steffen.klassert@secunet.com \
    --cc=svens@linux.ibm.com \
    --cc=tonylu@linux.alibaba.com \
    --cc=wenjia@linux.ibm.com \
    --cc=will@kernel.org \
    --cc=willy@infradead.org \
    --cc=yzaikin@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.