From: Gerd Bayer <gbayer@linux.ibm.com>
To: Simon Horman <horms@kernel.org>
Cc: Wenjia Zhang <wenjia@linux.ibm.com>,
Jan Karcher <jaka@linux.ibm.com>,
Tony Lu <tonylu@linux.alibaba.com>,
Paolo Abeni <pabeni@redhat.com>,
Karsten Graul <kgraul@linux.ibm.com>,
"D . Wythe" <alibuda@linux.alibaba.com>,
Wen Gu <guwen@linux.alibaba.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] net/smc: Fix effective buffer size
Date: Fri, 04 Aug 2023 17:41:13 +0200 [thread overview]
Message-ID: <129c1c96eaafd7d3e57b05ca96354ffc129fd4e3.camel@linux.ibm.com> (raw)
In-Reply-To: <ZM0IX/YnaawWT9sm@kernel.org>
On Fri, 2023-08-04 at 16:17 +0200, Simon Horman wrote:
> On Thu, Aug 03, 2023 at 04:46:03PM +0200, Gerd Bayer wrote:
> > Hi all,
> >
[...]
> > v1 - v2:
> > - In second patch, use sock_net() helper as suggested by Tony and
> > demanded
> > by kernel test robot.
> >
> > [1]
> > https://lore.kernel.org/netdev/20221123104907.14624-1-jaka@linux.ibm.com
>
> Hi Gerd,
>
> unfortunately this patchset does not appear to apply to current
> 'net'.
>
> Could you rebase and send a v3?
>
Hi Simon,
sure, working on it.
Thanks,
Gerd
prev parent reply other threads:[~2023-08-04 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 14:46 [PATCH net v2 0/2] net/smc: Fix effective buffer size Gerd Bayer
2023-08-03 14:46 ` [PATCH net v2 1/2] net/smc: Fix setsockopt and sysctl to specify same buffer size again Gerd Bayer
2023-08-03 14:46 ` [PATCH net v2 2/2] net/smc: Use correct buffer sizes when switching between TCP and SMC Gerd Bayer
2023-08-04 14:17 ` [PATCH net v2 0/2] net/smc: Fix effective buffer size Simon Horman
2023-08-04 15:41 ` Gerd Bayer [this message]
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=129c1c96eaafd7d3e57b05ca96354ffc129fd4e3.camel@linux.ibm.com \
--to=gbayer@linux.ibm.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=jaka@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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).