From: liweihang <liweihang@huawei.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: "dledford@redhat.com" <dledford@redhat.com>,
"leon@kernel.org" <leon@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>
Subject: Re: [PATCH v2 for-next 0/7] RDMA/core: Correct some coding-style issues
Date: Tue, 13 Apr 2021 02:37:50 +0000 [thread overview]
Message-ID: <38fd2d20d1634305818ba2d4786b05b0@huawei.com> (raw)
In-Reply-To: 20210412175937.GA1145318@nvidia.com
On 2021/4/13 2:00, Jason Gunthorpe wrote:
> On Wed, Apr 07, 2021 at 04:15:46PM +0800, Weihang Li wrote:
>> Do some cleanups according to the coding-style of kernel.
>>
>> Changes since v1:
>> - Remove a BUG_ON in #3 and put the changes into a new patch.
>> - Drop the parts about spaces around xx_for_each_xx() from #4 because some
>> clang formatter prefer current style.
>> - Link: https://patchwork.kernel.org/project/linux-rdma/cover/1617697184-48683-1-git-send-email-liweihang@huawei.com/
>
> Let's not make a habit of sending patches like this, but I will take
> this one
>
Sure.
>> Wenpeng Liang (6):
>> RDMA/core: Print the function name by __func__ instead of an fixed
>> string
>> RDMA/core: Remove the redundant return statements
>> RDMA/core: Add necessary spaces
>> RDMA/core: Remove redundant spaces
>
> I fixed the layout of most of the lines this patch touched as they
> were still not close enough to the canonical format.
>
OK, thank you.
Weihang
> Applied to for-next, thanks
>
> Jason
>
prev parent reply other threads:[~2021-04-13 2:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 8:15 [PATCH v2 for-next 0/7] RDMA/core: Correct some coding-style issues Weihang Li
2021-04-07 8:15 ` [PATCH v2 for-next 1/7] RDMA/core: Print the function name by __func__ instead of an fixed string Weihang Li
2021-04-07 8:15 ` [PATCH v2 for-next 2/7] RDMA/core: Remove the redundant return statements Weihang Li
2021-04-07 8:15 ` [PATCH v2 for-next 3/7] RDMA/core: Add necessary spaces Weihang Li
2021-04-07 8:15 ` [PATCH v2 for-next 4/7] RDMA/core: Remove redundant spaces Weihang Li
2021-04-07 8:15 ` [PATCH v2 for-next 5/7] RDMA/core: Correct format of braces Weihang Li
2021-04-07 8:15 ` [PATCH v2 for-next 6/7] RDMA/core: Correct format of block comments Weihang Li
2021-04-07 8:15 ` [PATCH v2 for-next 7/7] RDMA/core: Remove redundant BUG_ON Weihang Li
2021-04-12 17:51 ` Jason Gunthorpe
2021-04-13 3:46 ` liweihang
2021-04-07 12:26 ` [PATCH v2 for-next 0/7] RDMA/core: Correct some coding-style issues Leon Romanovsky
2021-04-12 17:59 ` Jason Gunthorpe
2021-04-13 2:37 ` liweihang [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=38fd2d20d1634305818ba2d4786b05b0@huawei.com \
--to=liweihang@huawei.com \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.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.