From: Dan Carpenter <dan.carpenter@oracle.com>
To: Cheng Xu <chengyou@linux.alibaba.com>
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Kai Shen <kaishen@linux.alibaba.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH 1/2] RDMA/erdma: Use the bitmap API to allocate bitmaps
Date: Tue, 12 Jul 2022 12:01:10 +0300 [thread overview]
Message-ID: <20220712090110.GL2338@kadam> (raw)
In-Reply-To: <670c57a2-6432-80c9-cdc0-496d836d7bf0@linux.alibaba.com>
On Mon, Jul 11, 2022 at 03:34:56PM +0800, Cheng Xu wrote:
>
>
> On 7/9/22 1:37 AM, Christophe JAILLET wrote:
> > Use [devm_]bitmap_zalloc()/bitmap_free() instead of hand-writing them.
> >
> > It is less verbose and it improves the semantic.
> >
> > Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> > ---
> > drivers/infiniband/hw/erdma/erdma_cmdq.c | 7 +++----
> > drivers/infiniband/hw/erdma/erdma_main.c | 9 ++++-----
> > 2 files changed, 7 insertions(+), 9 deletions(-)
> >
>
> Hi Christophe,
>
> Thanks for your two patches of erdma.
>
> The erdma code your got is our first upstreaming code, so I would like to squash your
> changes into the relevant commit in our next patchset to make the commit history cleaner.
>
> BTW, the coding style in the patches is OK, but has a little differences with clang-format's
> result. I will use the format from clang-format to minimize manual adjustments.
>
Best not to use any auto-formatting tools. They are all bad.
regards,
dan carpenter
next prev parent reply other threads:[~2022-07-12 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 17:37 [PATCH 1/2] RDMA/erdma: Use the bitmap API to allocate bitmaps Christophe JAILLET
2022-07-08 17:37 ` [PATCH 2/2] RDMA/erdma: Use the non-atomic bitmap API when applicable Christophe JAILLET
2022-07-11 7:34 ` [PATCH 1/2] RDMA/erdma: Use the bitmap API to allocate bitmaps Cheng Xu
2022-07-12 9:01 ` Dan Carpenter [this message]
2022-07-12 9:56 ` Cheng Xu
2022-07-19 12:54 ` Jason Gunthorpe
2022-07-19 13:01 ` Dan Carpenter
2022-07-19 15:36 ` Christophe JAILLET
2022-07-19 15:39 ` Jason Gunthorpe
2022-07-20 1:58 ` Cheng Xu
2022-07-21 7:31 ` Leon Romanovsky
2022-07-21 9:14 ` Cheng Xu
2022-07-21 7:27 ` Leon Romanovsky
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=20220712090110.GL2338@kadam \
--to=dan.carpenter@oracle.com \
--cc=chengyou@linux.alibaba.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jgg@ziepe.ca \
--cc=kaishen@linux.alibaba.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).