linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: Leon Romanovsky <leon@kernel.org>,
	"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
	dledford@redhat.com, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org, xavier.huwei@tom.com,
	xavier_huwei@163.com, linuxarm@huawei.com
Subject: Re: [PATCH 0/3] RDMA/hns: Bug fixes in hns RoCE driver
Date: Tue, 28 Nov 2017 11:39:10 -0700	[thread overview]
Message-ID: <20171128183910.GA21325@ziepe.ca> (raw)
In-Reply-To: <6e9c4251-8e56-54e2-b186-d3d5b1b85204@intel.com>

On Tue, Nov 28, 2017 at 08:20:09AM -0500, Dennis Dalessandro wrote:
> >
> >If you treat all unmarked patches (without mentioning in cover letter or
> >subject title) as targeted to for-next, it will make your life much more
> >easier than trying to pick each patch alone. As an outcome, it will make
> >the patch flow more predictable for us.

> 
> Agree with Leon here. Unless otherwise stated, I would think for-next should
> always be the default target. I try to tag my subject with for-next or
> for-rc to make it clear.

For Leon and Dennis I know they mark things, but other people seem to
be sending bug fixes that are rc material without any firm indication
one way or the other. I read the patches and that is my main question.

Of course if they do not come in RC acceptable format then they wait
in patchworks until -next is opened.

> Now of course that being said here is an exception. I sent a series 2 weeks
> ago that didn't make Doug's pull request for 4.15. I'd like to see some of
> that stuff land in the rc if there are no objections. The driver changes at
> least, the CM/SA can probably push off to for-next.
 
> I could resubmit just the series, or you could just pick the 4 driver
> patches from patchworks whatever is easiest.

I marked them in patchworks, but can you review the commit messages
and make sure you think Linus will see them as rc material too?

Thanks,
Jason

  reply	other threads:[~2017-11-28 18:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27  2:41 [PATCH 0/3] RDMA/hns: Bug fixes in hns RoCE driver Wei Hu (Xavier)
2017-11-27  2:41 ` [PATCH 1/3] RDMA/hns: Fix the issue of IOVA not page continuous in hip08 Wei Hu (Xavier)
2017-11-27  2:41 ` [PATCH 2/3] RDMA/hns: Get rid of virt_to_page and vmap calls after dma_alloc_coherent Wei Hu (Xavier)
2017-11-27  2:41 ` [PATCH 3/3] RDMA/hns: Get rid of page operation " Wei Hu (Xavier)
     [not found] ` <1511750484-102395-1-git-send-email-xavier.huwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-11-27 18:36   ` [PATCH 0/3] RDMA/hns: Bug fixes in hns RoCE driver Jason Gunthorpe
     [not found]     ` <20171127183637.GA13966-uk2M96/98Pc@public.gmane.org>
2017-11-28  6:15       ` Leon Romanovsky
2017-11-28 13:20         ` Dennis Dalessandro
2017-11-28 18:39           ` Jason Gunthorpe [this message]
     [not found]             ` <20171128183910.GA21325-uk2M96/98Pc@public.gmane.org>
2017-11-28 18:50               ` Bart Van Assche
     [not found]                 ` <1511895042.28512.6.camel-Sjgp3cTcYWE@public.gmane.org>
2017-11-28 19:08                   ` Leon Romanovsky
2017-11-28 19:33                 ` Jason Gunthorpe
     [not found]                   ` <20171128193311.GB21325-uk2M96/98Pc@public.gmane.org>
2017-11-28 20:27                     ` Dennis Dalessandro
     [not found]                       ` <c3d23cf8-ed10-73a3-7b5b-8c58b7aa4781-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-11-29 10:00                         ` Jonathan Cameron
2017-11-28  6:28       ` Wei Hu (Xavier)

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=20171128183910.GA21325@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=dennis.dalessandro@intel.com \
    --cc=dledford@redhat.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=xavier.huwei@huawei.com \
    --cc=xavier.huwei@tom.com \
    --cc=xavier_huwei@163.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;
as well as URLs for NNTP newsgroup(s).