From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: Zhu Yanjun <yanjun.zhu@linux.dev>,
linux-rdma@vger.kernel.org, "leon@kernel.org" <leon@kernel.org>
Subject: Re: [PATCH for-next v4 0/7] RDMA/rxe: Make multicast work
Date: Mon, 4 Dec 2023 20:08:32 -0400 [thread overview]
Message-ID: <20231205000832.GC2692119@nvidia.com> (raw)
In-Reply-To: <e91c7ff8-9c67-45e8-b28e-5bfa8c9e97da@gmail.com>
On Mon, Dec 04, 2023 at 06:02:55PM -0600, Bob Pearson wrote:
> After rereading v4 patch 0003 I noticed that I missed adding locks
> around ipv6_sock_mc_drop() in the error path in rxe_mcast_add6().
> Would you rather I send a new v4 patch or resend the series as v5?
Please send the whole thing, patchworks does not like it when
individual patches are revised
Thanks,
Jason
prev parent reply other threads:[~2023-12-05 0:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 20:03 [PATCH for-next v4 0/7] RDMA/rxe: Make multicast work Bob Pearson
2023-12-04 20:03 ` [PATCH for-next v4 1/7] RDMA/rxe: Cleanup rxe_ah/av_chk_attr Bob Pearson
2023-12-04 20:03 ` [PATCH for-next v4 2/7] RDMA/rxe: Fix sending of mcast packets Bob Pearson
2023-12-04 20:03 ` [PATCH for-next v4 3/7] RDMA/rxe: Register IP mcast address Bob Pearson
2023-12-04 20:03 ` [PATCH for-next v4 4/7] RDMA/rxe: Let rxe_lookup_mcg use rcu_read_lock Bob Pearson
2023-12-04 20:03 ` [PATCH for-next v4 5/7] RDMA/rxe: Split multicast lock Bob Pearson
2023-12-04 20:03 ` [PATCH for-next v4 6/7] RDMA/rxe: Cleanup mcg lifetime Bob Pearson
2023-12-04 20:03 ` [PATCH for-next v4 7/7] RDMA/rxe: Add module parameters for mcast limits Bob Pearson
2023-12-04 20:07 ` [PATCH for-next v4 0/7] RDMA/rxe: Make multicast work Bob Pearson
2023-12-04 23:50 ` Zhu Yanjun
2023-12-05 0:02 ` Bob Pearson
2023-12-05 0:08 ` Jason Gunthorpe [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=20231205000832.GC2692119@nvidia.com \
--to=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@gmail.com \
--cc=yanjun.zhu@linux.dev \
/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.