public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Brian King <brking@linux.vnet.ibm.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	"aneesh.kumar\@linux.vnet.ibm.com"
	<aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH] ipr: Fix sync scsi scan
Date: Wed, 10 Aug 2016 22:57:50 -0400	[thread overview]
Message-ID: <yq11t1wrp01.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <87vazaqw5k.fsf@concordia.ellerman.id.au> (Michael Ellerman's message of "Tue, 09 Aug 2016 16:44:07 +1000")

>>>>> "Michael" == Michael Ellerman <mpe@ellerman.id.au> writes:

>> Sorry about that. I fixed up async scan and managed to break sync
>> scan...
>> 
>> This patch fixes it on my box. Does it fix the issue for you as well?

Michael> Yes, thanks!

Michael> If you like here's a:

Michael> Tested-by: Michael Ellerman <mpe@ellerman.id.au>

Michael> It would be good if we can we get that to Linus sooner rather
Michael> than later.

Brian: This was a wee bit short of a real patch submission but I hand
applied it to 4.8/scsi-fixes.

-- 
Martin K. Petersen	Oracle Linux Engineering

      reply	other threads:[~2016-08-11  2:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05 23:21 [GIT PULL] first round of SCSI updates for the 4.7+ merge window James Bottomley
     [not found] ` <87popjshn6.fsf@concordia.ellerman.id.au>
2016-08-08 22:53   ` [PATCH] ipr: Fix sync scsi scan Brian King
2016-08-09  6:44     ` Michael Ellerman
2016-08-11  2:57       ` Martin K. Petersen [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=yq11t1wrp01.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=torvalds@linux-foundation.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