From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Finn Thain <fthain@telegraphics.com.au>,
Ondrej Zary <linux@rainbow-software.org>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi/mac_esp: Replace bogus memory barrier with spinlock
Date: Mon, 24 Apr 2017 19:29:41 -0400 [thread overview]
Message-ID: <yq1vaptfkpm.fsf@oracle.com> (raw)
In-Reply-To: <a3f6ae90-7115-c34c-3a7f-98084e0f7087@gmail.com> (Michael Schmitz's message of "Tue, 25 Apr 2017 11:25:56 +1200")
Michael,
> I must have missed that one - where was it posted to?
Usual bat channel:
https://patchwork.kernel.org/patch/9658369/
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-04-24 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-02 7:08 [PATCH] scsi/mac_esp: Replace bogus memory barrier with spinlock Finn Thain
2017-04-24 22:29 ` Martin K. Petersen
2017-04-24 23:25 ` Michael Schmitz
2017-04-24 23:29 ` Martin K. Petersen [this message]
2017-04-25 2:14 ` Michael Schmitz
2017-04-25 16:53 ` 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=yq1vaptfkpm.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=fthain@telegraphics.com.au \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=schmitzmic@gmail.com \
/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