From: Leon Romanovsky <leon@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-rdma@vger.kernel.org,
Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>,
linux-hardening@vger.kernel.org, gustavoars@kernel.org,
Jason Gunthorpe <jgg@ziepe.ca>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] IB/hfi1: kzalloc to kzalloc_flex
Date: Mon, 9 Mar 2026 11:52:54 +0200 [thread overview]
Message-ID: <20260309095254.GT12611@unreal> (raw)
In-Reply-To: <CAKxU2N_3dmBQPyD84GkyecxO=+5mQVVmSgY0jfGSugFtXvZ4UQ@mail.gmail.com>
On Sun, Mar 08, 2026 at 01:09:31PM -0700, Rosen Penev wrote:
> On Sun, Mar 8, 2026 at 9:00 AM Leon Romanovsky <leon@kernel.org> wrote:
> >
> > On Sat, Mar 07, 2026 at 07:19:56PM -0800, Rosen Penev wrote:
> > > Combine kzalloc and kcalloc with a flexible array member. Avoids having
> > > to free separately.
> > >
> > > Signed-off-by: Rosen Penev <rosenp@gmail.com>
> > > ---
> > > drivers/infiniband/hw/hfi1/user_exp_rcv.c | 10 +---------
> > > drivers/infiniband/hw/hfi1/user_exp_rcv.h | 2 +-
> > > 2 files changed, 2 insertions(+), 10 deletions(-)
> >
> > This patch needs to be rebased to latest rdma-next, due to the conflict
> > with already merged 94ff7c59cdfd ("RDMA: Complete k[z|m|c]alloc-to-k[z|m]alloc_obj conversion").
> https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/commit/?id=94ff7c59cdfd
>
> Notice: this object is not reachable from any branch.
>
> I'll take your word for it and rebase based on that.
You looked at my private repo, while the patch exist in official RDMA
repository.
https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/commit/?id=94ff7c59cdfd
Thanks
> >
> > Thanks
prev parent reply other threads:[~2026-03-09 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 3:19 [PATCH] IB/hfi1: kzalloc to kzalloc_flex Rosen Penev
2026-03-08 15:59 ` Leon Romanovsky
2026-03-08 20:09 ` Rosen Penev
2026-03-09 9:52 ` Leon Romanovsky [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=20260309095254.GT12611@unreal \
--to=leon@kernel.org \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=gustavoars@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rosenp@gmail.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.