From: Matthieu Baerts <matttbe@kernel.org>
To: Steffen Jaeckel <sjaeckel@suse.de>
Cc: Wenjia Zhang <wenjia@linux.ibm.com>,
Jan Karcher <jaka@linux.ibm.com>,
"D . Wythe" <alibuda@linux.alibaba.com>,
Tony Lu <tonylu@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>, Simon Horman <horms@kernel.org>,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Sidraya Jayagond <sidraya@linux.ibm.com>,
Alexandra Winter <wintera@linux.ibm.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH 1/1] dibs: Re-apply lost patch
Date: Tue, 27 Jan 2026 17:53:54 +0100 [thread overview]
Message-ID: <9e1100d7-87cf-4fd3-9840-028e63ffb184@kernel.org> (raw)
In-Reply-To: <20260127161611.2228083-1-sjaeckel@suse.de>
Hi Steffen,
On 27/01/2026 17:16, Steffen Jaeckel wrote:
> While merging the dibs layer, Matt [1] noticed that the changes which were
> done in [2] conflicted and were missing. He subsequently fixed this in the
> merge commit of his own tree, but the changes never made it upstream.
>
> This commit re-introduces the changes.
>
> [1] https://lore.kernel.org/netdev/74368a5c-48ac-4f8e-a198-40ec1ed3cf5f@kernel.org/
> [2] a35c04de2565d ("net/smc: fix warning in smc_rx_splice() when calling get_page()")
Thank you for the follow-up.
On which tree is this patch based on? Because I don't see the missing
resolution on net-next and even in Linus tree, see commit 203e3beb73e5
("Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net") or
check the file in Linus tree:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/dibs/dibs_loopback.c
Am I missing something?
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2026-01-27 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 16:16 [PATCH 1/1] dibs: Re-apply lost patch Steffen Jaeckel
2026-01-27 16:53 ` Matthieu Baerts [this message]
2026-01-28 8:23 ` Steffen Jaeckel
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=9e1100d7-87cf-4fd3-9840-028e63ffb184@kernel.org \
--to=matttbe@kernel.org \
--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=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=sidraya@linux.ibm.com \
--cc=sjaeckel@suse.de \
--cc=tonylu@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox