From: Jason Gunthorpe Subject: Re: [PATCH for-rc 0/3] Date: Tue, 26 Jun 2018 14:41:50 -0600 Message-ID: <20180626204150.GG5381@ziepe.ca> References: <20180620162612.13582.28777.stgit@scvm10.sc.intel.com> <20180620184323.GD27445@ziepe.ca> <98d77608-5b8d-3a2f-7721-9c3e176d4f0e@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <98d77608-5b8d-3a2f-7721-9c3e176d4f0e@intel.com> Sender: stable-owner@vger.kernel.org To: Dennis Dalessandro Cc: dledford@redhat.com, Mike Marciniszyn , linux-rdma@vger.kernel.org, stable@vger.kernel.org, "Michael J. Ruhl" , Dan Carpenter , Kamenee Arumugam List-Id: linux-rdma@vger.kernel.org On Tue, Jun 26, 2018 at 11:20:12AM -0400, Dennis Dalessandro wrote: > On 6/20/2018 2:43 PM, Jason Gunthorpe wrote: > >On Wed, Jun 20, 2018 at 09:28:39AM -0700, Dennis Dalessandro wrote: > >>Hi Doug and Jason, > >> > >>Here are a couple patches that we'd like to get into 4.18 rc cycle. These fix > >>bugs and aren't too complex. One of them is an issue that Dan Carpenter just > >>reported recently and is marked for stable. > > > >All of these need Fixes lines for-rc and other than the last one the > >commit messages are not good enough - talk about what user visible > >effect this bug has. > > I talked to Mike and we are good with pushing the first two off till > for-next. We'll make some commit message improvements and send a v2 for > those. They could be OK to go to for-rc, but they need to meet the standard, and I can't tell from the commit message. I've dropped them from patchworks, so resend V2. Jason