[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1511895042.28512.6.camel@wdc.com>
Date: Tue, 28 Nov 2017 18:50:44 +0000
From: Bart Van Assche <Bart.VanAssche@....com>
To: "jgg@...pe.ca" <jgg@...pe.ca>,
"dennis.dalessandro@...el.com" <dennis.dalessandro@...el.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"xavier_huwei@....com" <xavier_huwei@....com>,
"linuxarm@...wei.com" <linuxarm@...wei.com>,
"xavier.huwei@...wei.com" <xavier.huwei@...wei.com>,
"xavier.huwei@....com" <xavier.huwei@....com>,
"leon@...nel.org" <leon@...nel.org>,
"dledford@...hat.com" <dledford@...hat.com>
Subject: Re: [PATCH 0/3] RDMA/hns: Bug fixes in hns RoCE driver
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.
Powered by blists - more mailing lists