From: Jakub Kicinski <kuba@kernel.org>
To: Gerd Bayer <gbayer@linux.ibm.com>
Cc: Niklas Schnelle <schnelle@linux.ibm.com>,
"David S.Miller" <davem@davemloft.net>,
wintera@linux.ibm.com, twinkler@linux.ibm.com, hca@linux.ibm.com,
pabeni@redhat.com, hch@lst.de, pasic@linux.ibm.com,
wenjia@linux.ibm.com, guwen@linux.alibaba.com,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
gor@linux.ibm.com, agordeev@linux.ibm.com,
borntraeger@linux.ibm.com, svens@linux.ibm.com
Subject: Re: [PATCH net v2] s390/ism: fix receive message buffer allocation
Date: Mon, 8 Apr 2024 12:46:09 -0700 [thread overview]
Message-ID: <20240408124609.4ca811f2@kernel.org> (raw)
In-Reply-To: <7e6baff2338ef4c3af9073c46b5492f271bdd9ae.camel@linux.ibm.com>
On Mon, 08 Apr 2024 21:05:47 +0200 Gerd Bayer wrote:
> Hi Dave,
Hi, from the Dave replacement service.
> so how do we go forward? Would you revert this v2 in the netdev tree to
> have my next v3 properly reviewed?
>
> Second best option: I can send a fixup to address the last issue from
> [0], but that would still leave some pieces sent with (v1/v2) not
> properly R-by'd or at least ack'd.
If there's a chance we can get an incremental fix ready to merge by
Wednesday morning, let's try that. If we fail please post a revert by
Wednesday morning. On Thu morning EU time we'll ship the fixes to Linus,
so we gotta have the tree in a good share at that point.
next prev parent reply other threads:[~2024-04-08 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 11:16 [PATCH net v2] s390/ism: fix receive message buffer allocation Gerd Bayer
2024-04-08 11:00 ` patchwork-bot+netdevbpf
2024-04-08 12:40 ` Niklas Schnelle
2024-04-08 19:05 ` Gerd Bayer
2024-04-08 19:46 ` Jakub Kicinski [this message]
2024-04-09 7:58 ` Gerd Bayer
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=20240408124609.4ca811f2@kernel.org \
--to=kuba@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=gbayer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=guwen@linux.alibaba.com \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=schnelle@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=twinkler@linux.ibm.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@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 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.