public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Rohit Chavan <roheetchavan@gmail.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/mlx5: Coding style fix
Date: Wed, 22 Feb 2023 10:03:54 +0200	[thread overview]
Message-ID: <Y/XMao1jNTbK0GE5@unreal> (raw)
In-Reply-To: <20230220122116.2047-1-roheetchavan@gmail.com>

On Mon, Feb 20, 2023 at 05:51:16PM +0530, Rohit Chavan wrote:
> Signed-off-by: Rohit Chavan <roheetchavan@gmail.com>
> ---
>  drivers/infiniband/hw/mlx5/qp.c | 9 ++++-----
>  1 file changed, 4 insertions(+), 5 deletions(-)


Please try to avoid empty commit messages.

And we are in merge window now, so new version of this patch will need
to wait till -rc1.

Thanks

      reply	other threads:[~2023-02-22  8:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 12:21 [PATCH] RDMA/mlx5: Coding style fix Rohit Chavan
2023-02-22  8:03 ` 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=Y/XMao1jNTbK0GE5@unreal \
    --to=leon@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=roheetchavan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox