From: Krystian Kaniewski <krystianmkaniewski@gmail.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Jakub Kicinski <kuba@kernel.org>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com,
syzbot+5fe14f2ff4ccbace9a26@syzkaller.appspotmail.com
Subject: Re: [PATCH net v3] RDMA/core: Reject unregistering netdevs in ib_get_eth_speed
Date: Wed, 12 Aug 2026 10:19:09 +0200 [thread overview]
Message-ID: <8a15a6d9-20b0-4fe2-b96e-9b9371eb1831@gmail.com> (raw)
In-Reply-To: <20260811163025.GM544626@ziepe.ca>
Thanks. I have sent v4 patch rebased on top of for-next branch just a
moment ago.
On 8/11/2026 6:30 PM, Jason Gunthorpe wrote:
> On Tue, Aug 11, 2026 at 11:21:19AM +0200, Krystian Kaniewski wrote:
>> Thanks for your comments. It's my first contribution really, so I'm still
>> learning on how to do it properly.
>>
>> I'll do the requested changes by both of you.
>>
>> Should I rebase the v4 patch on top of any specific branches for rdma?
>>
>> I found "for-rc" branch while looking at
>> https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git, would it be a
>> good target?
> At this point the for-next branch is a better choice
>
> Jason
prev parent reply other threads:[~2026-08-12 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 13:31 [PATCH net v3] RDMA/core: Reject unregistering netdevs in ib_get_eth_speed Krystian Kaniewski
2026-08-10 13:42 ` Jason Gunthorpe
2026-08-10 18:33 ` Jakub Kicinski
2026-08-10 18:39 ` Jason Gunthorpe
2026-08-11 9:21 ` Krystian Kaniewski
2026-08-11 16:30 ` Jason Gunthorpe
2026-08-12 8:19 ` Krystian Kaniewski [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=8a15a6d9-20b0-4fe2-b96e-9b9371eb1831@gmail.com \
--to=krystianmkaniewski@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+5fe14f2ff4ccbace9a26@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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