From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: dledford@redhat.com,
Mike Marciniszyn <mike.marciniszyn@intel.com>,
linux-rdma@vger.kernel.org, stable@vger.kernel.org,
"Michael J. Ruhl" <michael.j.ruhl@intel.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Kamenee Arumugam <kamenee.arumugam@intel.com>
Subject: Re: [PATCH for-rc 0/3]
Date: Tue, 26 Jun 2018 14:41:50 -0600 [thread overview]
Message-ID: <20180626204150.GG5381@ziepe.ca> (raw)
In-Reply-To: <98d77608-5b8d-3a2f-7721-9c3e176d4f0e@intel.com>
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
prev parent reply other threads:[~2018-06-26 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 16:28 [PATCH for-rc 0/3] Dennis Dalessandro
2018-06-20 16:29 ` [PATCH for-rc 3/3] IB/hfi1: Fix incorrect mixing of ERR_PTR and NULL return values Dennis Dalessandro
2018-06-26 15:19 ` Dennis Dalessandro
2018-06-26 20:37 ` Jason Gunthorpe
2018-06-20 16:33 ` [PATCH for-rc 0/3] Dennis Dalessandro
2018-06-20 18:43 ` Jason Gunthorpe
2018-06-26 15:20 ` Dennis Dalessandro
2018-06-26 20:41 ` Jason Gunthorpe [this message]
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=20180626204150.GG5381@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dan.carpenter@oracle.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=kamenee.arumugam@intel.com \
--cc=linux-rdma@vger.kernel.org \
--cc=michael.j.ruhl@intel.com \
--cc=mike.marciniszyn@intel.com \
--cc=stable@vger.kernel.org \
/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).