All of lore.kernel.org
 help / color / mirror / Atom feed
From: liweihang <liweihang@huawei.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
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 for-next] RDMA/hns: Remove unused variables and definitions
Date: Mon, 28 Sep 2020 12:27:56 +0000	[thread overview]
Message-ID: <191e848eff4840ef80d9fbb0eab064a8@huawei.com> (raw)
In-Reply-To: 20200928115547.GL9916@ziepe.ca

On 2020/9/28 19:55, Jason Gunthorpe wrote:
> On Sun, Sep 27, 2020 at 05:52:21PM +0800, Weihang Li wrote:
>> From: Lang Cheng <chenglang@huawei.com>
>>
>> Some code was removed but the variables were still there, and some
>> parameters have been changed to be queried from firmware. So the
>> definitions of them are no longer needed.
>>
>> Signed-off-by: Lang Cheng <chenglang@huawei.com>
>> Signed-off-by: Weihang Li <liweihang@huawei.com>
>> ---
>>  drivers/infiniband/hw/hns/hns_roce_device.h | 8 --------
>>  drivers/infiniband/hw/hns/hns_roce_qp.c     | 2 --
>>  2 files changed, 10 deletions(-)
> 
> Should have a fixes for the patch that removed the code
> 
> Jason
> 

Hi Jason,

Thanks for the comment. But I'm confused about when we should add
fixes tag.

For example, The only purpose of this patch is to remove redundant
macro definitions, the macros to be removed belong to 4 different
former patches, so we have to add 4 lines of fixes. It seems difficult
to merge this one back to previous versions of kernel.

Should I split this patch into 4 patches and add a fixes tag for each
one, or just put all these fixes tag in this patch?

Thanks
Weihang

  reply	other threads:[~2020-09-28 12:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-27  9:52 [PATCH for-next] RDMA/hns: Remove unused variables and definitions Weihang Li
2020-09-28 11:55 ` Jason Gunthorpe
2020-09-28 12:27   ` liweihang [this message]
2020-09-28 12:50     ` Jason Gunthorpe
2020-09-28 12:58       ` liweihang

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=191e848eff4840ef80d9fbb0eab064a8@huawei.com \
    --to=liweihang@huawei.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --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.