From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "jgg@ziepe.ca" <jgg@ziepe.ca>,
"dennis.dalessandro@intel.com" <dennis.dalessandro@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"xavier_huwei@163.com" <xavier_huwei@163.com>,
"linuxarm@huawei.com" <linuxarm@huawei.com>,
"xavier.huwei@huawei.com" <xavier.huwei@huawei.com>,
"xavier.huwei@tom.com" <xavier.huwei@tom.com>,
"leon@kernel.org" <leon@kernel.org>,
"dledford@redhat.com" <dledford@redhat.com>
Subject: Re: [PATCH 0/3] RDMA/hns: Bug fixes in hns RoCE driver
Date: Tue, 28 Nov 2017 18:50:44 +0000 [thread overview]
Message-ID: <1511895042.28512.6.camel@wdc.com> (raw)
In-Reply-To: <20171128183910.GA21325@ziepe.ca>
On Tue, 2017-11-28 at 11:39 -0700, Jason Gunthorpe wrote:
> On Tue, Nov 28, 2017 at 08:20:09AM -0500, Dennis Dalessandro wrote:
> > 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?
My understanding is that the rc stage is intended primarily for fixes for
bugs introduced during the merge window. For all patches that do not fix
bugs introduced during the merge window it should be evaluated carefully
whether or not these are important enough to be included in a rc pull request.
Bart.
next prev parent reply other threads:[~2017-11-28 18:50 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)
2017-11-27 18:36 ` [PATCH 0/3] RDMA/hns: Bug fixes in hns RoCE driver Jason Gunthorpe
2017-11-28 6:15 ` Leon Romanovsky
2017-11-28 13:20 ` Dennis Dalessandro
2017-11-28 18:39 ` Jason Gunthorpe
2017-11-28 18:50 ` Bart Van Assche [this message]
2017-11-28 19:08 ` Leon Romanovsky
2017-11-28 19:33 ` Jason Gunthorpe
2017-11-28 20:27 ` Dennis Dalessandro
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=1511895042.28512.6.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--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