All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg KH)
Subject: [PATCH v3 01/16] lpfc: Correct WQ creation for pagesize
Date: Tue, 7 Mar 2017 20:57:04 +0100	[thread overview]
Message-ID: <20170307195704.GB25619@kroah.com> (raw)
In-Reply-To: <7c6d6f3b-330c-ea6f-ad3f-65479354c94d@linux.vnet.ibm.com>

On Tue, Mar 07, 2017@10:44:51AM -0300, Mauricio Faria de Oliveira wrote:
> Hello stable kernel maintainers,
> 
> On 03/07/2017 12:35 AM, Martin K. Petersen wrote:
> > Mauricio> Please flag this patch for stable.
> > 
> > Mauricio> This patch resolves a serious problem on IBM Power systems at
> > Mauricio> least.
> > 
> > Both patches are already upstream so I can't tag them for stable. Either
> > you or James should mail stable at vger.kernel.org and request for the
> > patches to be queued up.
> 
> Can this commit be included on stable v4.4+ , please? (in Linus tree)
> 
>     8ea73db486cda442f0671f4bc9c03a76be398a28 "scsi: lpfc: Correct WQ
> creation for pagesize"

I need an ack from a scsi maintainer that this is an ok thing to do
before I can do so.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	stable@vger.kernel.org, James Smart <jsmart2021@gmail.com>,
	linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org,
	sagi@grimberg.me
Subject: Re: [PATCH v3 01/16] lpfc: Correct WQ creation for pagesize
Date: Tue, 7 Mar 2017 20:57:04 +0100	[thread overview]
Message-ID: <20170307195704.GB25619@kroah.com> (raw)
In-Reply-To: <7c6d6f3b-330c-ea6f-ad3f-65479354c94d@linux.vnet.ibm.com>

On Tue, Mar 07, 2017 at 10:44:51AM -0300, Mauricio Faria de Oliveira wrote:
> Hello stable kernel maintainers,
> 
> On 03/07/2017 12:35 AM, Martin K. Petersen wrote:
> > Mauricio> Please flag this patch for stable.
> > 
> > Mauricio> This patch resolves a serious problem on IBM Power systems at
> > Mauricio> least.
> > 
> > Both patches are already upstream so I can't tag them for stable. Either
> > you or James should mail stable@vger.kernel.org and request for the
> > patches to be queued up.
> 
> Can this commit be included on stable v4.4+ , please? (in Linus tree)
> 
>     8ea73db486cda442f0671f4bc9c03a76be398a28 "scsi: lpfc: Correct WQ
> creation for pagesize"

I need an ack from a scsi maintainer that this is an ok thing to do
before I can do so.

thanks,

greg k-h

  reply	other threads:[~2017-03-07 19:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-12 21:52 [PATCH v3 01/16] lpfc: Correct WQ creation for pagesize James Smart
2017-02-12 21:52 ` James Smart
2017-03-04  1:43 ` Mauricio Faria de Oliveira
2017-03-04  1:43   ` Mauricio Faria de Oliveira
2017-03-07  3:35   ` Martin K. Petersen
2017-03-07  3:35     ` Martin K. Petersen
2017-03-07 12:46     ` Mauricio Faria de Oliveira
2017-03-07 12:46       ` Mauricio Faria de Oliveira
2017-03-07 13:44     ` Mauricio Faria de Oliveira
2017-03-07 13:44       ` Mauricio Faria de Oliveira
2017-03-07 19:57       ` Greg KH [this message]
2017-03-07 19:57         ` Greg KH
2017-03-08  1:26         ` Martin K. Petersen
2017-03-08  1:26           ` Martin K. Petersen

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=20170307195704.GB25619@kroah.com \
    --to=gregkh@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.